You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue happens with a Helm operator. We have been seeing it recently, which makes us think of a regression from either operator-sdk 1.33.0 or GKE 1.27.
What did you do?
Create a custom resource as input to the operator with ArgoCD
Wait for the operator to install the Helm release
At this point, the helm release is visible and the corresponding secret present in the namespace.
Delete the resource using ArgoCD
What did you expect to see?
The Helm release should not disappear until all resources have been removed.
After the CR has been removed, the operator should be able to properly remove the resources
What did you see instead? Under which circumstances?
The Helm release disappears (helm list and kubectl get secrets both stop showing the release)
The operator displays the following:
{"level":"info","ts":"2024-01-26T13:18:58Z","logger":"helm.controller","msg":"Release not found","namespace":"namespaces","name":"zoom-s001","apiVersion":"charts.symphony.com/v1alpha1","kind":"ExtendedNamespace","release":"zoom-s001"}
{"level":"info","ts":"2024-01-26T13:18:58Z","logger":"helm.controller","msg":"Removing finalizer","namespace":"namespaces","name":"zoom-s001","apiVersion":"charts.symphony.com/v1alpha1","kind":"ExtendedNamespace","release":"zoom-s001"}
The resources deployed by the chart are still there, even though the CR has been fully deleted
At this point we need to manually remove the leftovers.
Could you post what your CRs look like, both the operand and the ArgoCD one? It it created with finalizers on the dependent resources or owner references? It's a bit hard to follow what exactly is happening from the information you've posted.
Hey we're going to close this due to inactivity. If you're still experiencing this issue please reopen it with the requested information so we can take a look at it.
Bug Report
This issue happens with a Helm operator. We have been seeing it recently, which makes us think of a regression from either operator-sdk 1.33.0 or GKE 1.27.
What did you do?
What did you expect to see?
What did you see instead? Under which circumstances?
helm list
andkubectl get secrets
both stop showing the release)Environment
Operator type:
Kubernetes cluster type:
GKE
$ operator-sdk version
1.33.0
$ go version
(if language is Go)1.21
$ kubectl version
Possible Solution
As a way to mitigate the impact: don't remove the finalizer in this case.
Additional context
Upgrade to GKE 1.27 (from 1.26) was done recently
The text was updated successfully, but these errors were encountered: