Closed pjestin-sym closed 1 month ago
I found a workaround using the uninstall-wait
annotation described here: https://sdk.operatorframework.io/docs/building-operators/helm/reference/advanced_features/annotations/#helmsdkoperatorframeworkiouninstall-wait
This helps mitigate the impact, although the issue probably will remain.
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.
Thanks!
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