Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add additional checks before PVC deletion #737

Open
burmanm opened this issue Dec 12, 2024 · 0 comments · May be fixed by #738
Open

Add additional checks before PVC deletion #737

burmanm opened this issue Dec 12, 2024 · 0 comments · May be fixed by #738
Assignees
Labels
enhancement New feature or request

Comments

@burmanm
Copy link
Contributor

burmanm commented Dec 12, 2024

What is missing?

While Kubernetes has pvc-protection that checks if PersistentVolumeClaim is still used by a pod, we could do the same before issuing pvc deletion.

Why is this needed?

In some cases (such as migrations / error cases / restore failures), users might have had orphaned pods + PVCs and the generated CassandraDatacenter wasn't correct. Deleting this CassandraDatacenter might have deleted the PVCs also as their name pair (clusterName + datacenterName) will match the PVCs, even if the Pods themselves are not actually part of the datacenter.

Thus, lets prevent this from happening and prevent the PVC deletion if a PVC is actually still in use.

┆Issue is synchronized with this Jira Story by Unito
┆Issue Number: CASS-82

@burmanm burmanm added the enhancement New feature or request label Dec 12, 2024
@burmanm burmanm linked a pull request Dec 12, 2024 that will close this issue
5 tasks
@burmanm burmanm self-assigned this Dec 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
No open projects
Status: No status
Development

Successfully merging a pull request may close this issue.

1 participant