releases not deleting when in composition with a gke cluster
rmossuk opened this issue · 2 comments
What happened?
When i have a XR and the composition contains a cluster (gke), helm provider config and helm charts, when i delete the XR it should remove all releases (releases.helm.crossplane.io).
it starts deleting the cluster or the kubeconfig secret before helm provider has a chance to clean up. Error message failed to extract kubeconfig: cannot get credentials secret: Secret "f70c8c2a-4be7-46eb-8487-a78333a6dd02-gke-cluster" not found
How can we reproduce it?
Create a gke cluster, nodepool, helm-provider-config and some helm charts into the composition of an XR. Then delete the XR.
What environment did it happen in?
Crossplane version: 1.5.0
This is similar to crossplane-contrib/provider-kubernetes#38 and is a general problem when provisioning resources into a K8S cluster that has been created in the same composition. It slows down the provider to the point where it is essentially unusable. There needs to be a way for the provider to clean up these resources when they have been marked deleted.
crossplane/crossplane#3393 proposes a generic solution for these issues