Commit ec330895 authored by Zach Loafman's avatar Zach Loafman

AWS: Handle kube-down case where the LaunchConfig is dangling

Always query and attempt to delete the default launch-config
parent ec7c58ed
...@@ -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
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment