Super weird, destroying a cluster with AWS elb CDR’s, destroyed the nodepool, but left the CRD instances (not deployed via this stack) deadlocking the deploy completely. The CRD would not delete as stuff was still using it so the destroy fails. Apart from destroying in the right order, any way to prevent this deadlocking?

you need to destroy in the right order, using

dependsOn

hmm, we are using the official helm charts from aws so targetting the crd inside is not trivial, and the crd’s are used in a different stack. dependsOn does not work cross stack right?

Generally I try and install the crd outside the helm chart for this reason