-
Notifications
You must be signed in to change notification settings - Fork 66
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
CRDs are not deleted when provider is removed #120
Comments
After some consideration it seems like a bad idea, because we will also need to delete all user created objects like Cluster or Machine. |
After some consideration it seems like a good idea, but we need to differentiate scenarios when we delete resources during provider upgrade, and when we delete the provider itself completely. |
Another option is to introduce a deletion policy API field, which doesn't remove CRDs by default |
/triage accepted |
This issue has not been updated in over 1 year, and should be re-triaged. You can:
For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/ /remove-triage accepted |
What steps did you take and what happened:
cluster.x-k8s.io
are not deleted together with the provider.What did you expect to happen:
All created resources should be removed.
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
Environment:
kubectl version
): 1.27/etc/os-release
):/kind bug
[One or more /area label. See https://github.com/kubernetes-sigs/cluster-api-operator/labels?q=area for the list of labels]
The text was updated successfully, but these errors were encountered: