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

Always query and attempt to delete the default launch-config
lavalamp · Aug 17, 2016 · ec33089 · ec33089
1 parent ec7c58e
commit ec33089
Showing 1 changed file with 5 additions and 0 deletions.
diff --git a/cluster/aws/util.sh b/cluster/aws/util.sh
@@ -1345,6 +1345,11 @@ function kube-down {
       done
       echo "All instances deleted"
     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-tagged-master-ip