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

Prevent deletion of resources created on behalf of the operator. #387

Closed
sdudoladov opened this issue Sep 17, 2018 · 1 comment
Closed

Comments

@sdudoladov
Copy link
Member

sdudoladov commented Sep 17, 2018

We've had cases when users manually deleted pods/statefulsets/etc of a PG cluster only to found out them to be re-created later. This leads to users' confusion and extra debugging overhead for maintenance teams. We should experiment with k8s finalizers available since k8s v1.11 to prevent such deletions. Things to watch out are (a) properly handling the deletion timestamp (is set on the first delete request ), (b) effectively informing users about why their deletions of operator managed resources do not succeed and (c) enabling members of admin teams manually delete misbehaving resources.

A more sophisticated option is to use k8s admission webhooks.

@FxKu
Copy link
Member

FxKu commented Apr 24, 2024

Closing this tickets since finalizers support has been added.

@FxKu FxKu closed this as completed Apr 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants