Skip to content
Projects
Groups
Snippets
Help
This project
Loading...
Sign in / Register
Toggle navigation
K
k3s
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Registry
Registry
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Jacklull
k3s
Commits
ec330895
Commit
ec330895
authored
Aug 17, 2016
by
Zach Loafman
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
AWS: Handle kube-down case where the LaunchConfig is dangling
Always query and attempt to delete the default launch-config
parent
ec7c58ed
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
5 additions
and
0 deletions
+5
-0
util.sh
cluster/aws/util.sh
+5
-0
No files found.
cluster/aws/util.sh
View file @
ec330895
...
@@ -1345,6 +1345,11 @@ function kube-down {
...
@@ -1345,6 +1345,11 @@ function kube-down {
done
done
echo
"All instances deleted"
echo
"All instances deleted"
fi
fi
if
[[
-n
$(${
AWS_ASG_CMD
}
describe-launch-configurations
--launch-configuration-names
${
ASG_NAME
}
--query
LaunchConfigurations[].LaunchConfigurationName
)
]]
;
then
echo
"Warning: default auto-scaling launch configuration
${
ASG_NAME
}
still exists, attempting to delete"
echo
" (This may happen if kube-up leaves just the launch configuration but no auto-scaling group.)"
${
AWS_ASG_CMD
}
delete-launch-configuration
--launch-configuration-name
${
ASG_NAME
}
||
true
fi
find-master-pd
find-master-pd
find-tagged-master-ip
find-tagged-master-ip
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment