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

[FEATURE] - Namespace Protection #688

Merged
merged 1 commit into from
Apr 17, 2023
Merged

[FEATURE] - Namespace Protection #688

merged 1 commit into from
Apr 17, 2023

Conversation

gambol99
Copy link
Member

@gambol99 gambol99 commented Apr 17, 2023

Currently you can get into a situation where deleting a namespace before a Configurations have been removed causes the namespace to fall into a Termination failure. The issue is caused by terranetes trying to create a watcher to watch the deletion. With this PR we've added a protection layer to block namespaces from being deleted when one or more Configurations are present.

The feature is disbled by default, to enable you have to configure enableNamespaceProtection: true in the helm chart or ---enable-namespace-protection=true on command line.

Currently you can get into a situation where deleting a namespace before a Configurations have been removed causes the namespace to fall into a Termination failure. The issue is caused by terranetes trying to create a watcher to watch the deletion. With this PR we've added a protection layer to block namespaces from being deleted when one or more Configurations are present
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Termination of namespace gets stuck if cloud resource can't be cleaned up
1 participant