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
What happened?
If there's no finalizer present, we shouldn't do our finalizer processing. This means deletion of PVCs, blocking deletion and possibly decommission a datacenter (among other things).
However, we add finalizer in our process if it is removed. As such, we need an annotation that prevents the re-adding of that annotation (or even adding it at all).
Did you expect to see something different?
How to reproduce it (as minimally and precisely as possible):
Environment
Cass Operator version:
Insert image tag or Git SHA here
* Kubernetes version information:
kubectl version
* Kubernetes cluster kind:
insert how you created your cluster: kops, bootkube, etc.
Manifests:
insert manifests relevant to the issue
Cass Operator Logs:
insert Cass Operator logs relevant to the issue here
Anything else we need to know?:
┆Issue is synchronized with this Jira Task by Unito
┆friendlyId: K8SSAND-1645
┆priority: Medium
The text was updated successfully, but these errors were encountered:
sync-by-unitobot
changed the title
If no finalizer is present, skip deletion process
K8SSAND-1645 ⁃ If no finalizer is present, skip deletion process
Jul 12, 2022
What happened?
If there's no finalizer present, we shouldn't do our finalizer processing. This means deletion of PVCs, blocking deletion and possibly decommission a datacenter (among other things).
However, we add finalizer in our process if it is removed. As such, we need an annotation that prevents the re-adding of that annotation (or even adding it at all).
Did you expect to see something different?
How to reproduce it (as minimally and precisely as possible):
Environment
Cass Operator version:
* Kubernetes version information:Insert image tag or Git SHA here
* Kubernetes cluster kind:kubectl version
Anything else we need to know?:
┆Issue is synchronized with this Jira Task by Unito
┆friendlyId: K8SSAND-1645
┆priority: Medium
The text was updated successfully, but these errors were encountered: