-
Notifications
You must be signed in to change notification settings - Fork 295
unknown command "node-pools" for "kube-aws" with v0.9.5-rc.6 #539
Comments
Hi @cmcconnell1, thanks as always for trying kube-aws! Anyway, since v0.9.5, |
Hello @mumoshu AIR, I initially did try to just do a
I got in a bit of a mess by manually trying to purge, detach, disassociate resources that I saw in the CF event logs. |
Another note for anyone getting stuck with orphaned kube cluster infrastructure components (especially those using deis workflow) is that you will want to delete and un-munge anything done outside of kube-aws--including IAM roles you might have applied to cluster resources; your deis ELB, etc., before destroying your kube cluster. Else the Deis ELB persists and has a network interface associated and it's contained within a kube cluster subnet. So these will fail to delete and cause your cnf stack to fail upon delete, and ultimately prevents any clean
|
Note: Confirmed to work with v0.9.6-rc.2 according to #189 (comment) Thanks for your confirmation @cmcconnell1 👍 |
Also - thanks for the tips! I believe it should be noted in our documentation. I'll open an another issue to track the documentation. |
Hello
I'm running into an issue wherein I'm not able to delete the node pool according to the docs tagged with this release version as noted below.
Please let me know if I'm missing something.
Thanks!
According to the docs tagged for this release Destroy the cluster
so going from the docs, the command to delete the node pool should be:
However, when I try to run that command, it seems like it's not a valid sub-command/option?
I know this worked before testing node-pools with a previous version and validating from my shell history
I still had an older version of kube-aws to validate this with
Was hoping I might be able to use the older version to delete my node-pools created with a newer version of kube-aws (that seems to be missing the node-pool sub-command), but seems like perhaps the node-pools configuration has changed and now it is in the main cluster.yaml file versus in sub directories
To move forward created the nested sub-dirs and copied the cluster.yaml file into the tree and then deleted the node-pools again with the older kube-aws version
The text was updated successfully, but these errors were encountered: