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

Delete resource should have an option to choose the deletion cascading strategy #8959

Open
jenting opened this issue Apr 23, 2024 · 3 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@jenting
Copy link

jenting commented Apr 23, 2024

What would you like to be added?

On the delete resource dialog, provide an optional to make user choose the deletion cascading strategy ("background", "foreground", or "orphan"). Default is "background".

Why is this needed?

The Kubernetes can't increase the PVC size of the StatefulSet volumeClaimTemplates automatically because of the issue. To increase the PVC size of the StatefulSet volumeClaimTemplates without downtime, we have to

  1. Orphan delete the StatefulSet to make the Pod+PVC running (remove the StatefulSet resource only).
  2. kubectl apply the new StatefulSet with new volumeClaimTemplates PVC size.

It would be good that the Kubernetes dashboard UI can support different deletion cascading strategy so we would not have to rely on the kubectl command to achieve above.

@jenting jenting added the kind/feature Categorizes issue or PR as related to a new feature. label Apr 23, 2024
@MiirzaBaig
Copy link

Is this issue still on?
I would like to contribute to this...

@jenting
Copy link
Author

jenting commented Apr 24, 2024

@MiirzaBaig
We haven't verified the latest version, we are using v2.7.0 now.

However, we did the code check and did not find the corresponding code. So we think this issue is still open.

@MiirzaBaig
Copy link

Ohkayy, cool..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

2 participants