-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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 kube-system as an immortal namespace #17808
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: liggitt The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
@@ -198,7 +198,7 @@ func newAdmissionChain(pluginNames []string, admissionConfigFilename string, opt | |||
switch pluginName { | |||
case lifecycle.PluginName: | |||
// We need to include our infrastructure and shared resource namespaces in the immortal namespaces list | |||
immortalNamespaces := sets.NewString(metav1.NamespaceDefault) | |||
immortalNamespaces := sets.NewString(metav1.NamespaceDefault, metav1.NamespaceSystem) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This still isn't in sync with upstream. They have NamespacePublic
protected too.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't actually care about public… I care about the namespaces which, when deleted, require cluster-admin intervention
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't really object to public either
opened #17914 as an alternative in head. |
closing in favor of #17914 |
Automatic merge from submit-queue (batch tested with PRs 17914, 18021, 18022, 17862, 18043). stop special casing creation for ns lifecycle admission alternative to #17808 When running an openshift server, the admission plugin will always want to protect the openshift namespace. This simplifies the admission chain creation path. Only three left.
Automatic merge from submit-queue (batch tested with PRs 17914, 18021, 18022, 17862, 18043). stop special casing creation for ns lifecycle admission alternative to openshift/origin#17808 When running an openshift server, the admission plugin will always want to protect the openshift namespace. This simplifies the admission chain creation path. Only three left. Origin-commit: f39d2243f75911085ea4b2c379adfae82c0c2011
Automatic merge from submit-queue (batch tested with PRs 17914, 18021, 18022, 17862, 18043). stop special casing creation for ns lifecycle admission alternative to openshift/origin#17808 When running an openshift server, the admission plugin will always want to protect the openshift namespace. This simplifies the admission chain creation path. Only three left. Origin-commit: f39d2243f75911085ea4b2c379adfae82c0c2011
Automatic merge from submit-queue (batch tested with PRs 17914, 18021, 18022, 17862, 18043). stop special casing creation for ns lifecycle admission alternative to openshift/origin#17808 When running an openshift server, the admission plugin will always want to protect the openshift namespace. This simplifies the admission chain creation path. Only three left. Origin-commit: f39d2243f75911085ea4b2c379adfae82c0c2011
Automatic merge from submit-queue (batch tested with PRs 17914, 18021, 18022, 17862, 18043). stop special casing creation for ns lifecycle admission alternative to openshift/origin#17808 When running an openshift server, the admission plugin will always want to protect the openshift namespace. This simplifies the admission chain creation path. Only three left. Origin-commit: f39d2243f75911085ea4b2c379adfae82c0c2011 Kubernetes-commit: 5d6c9e7ad44fbe3a6ba78153b11501903394ab5b
No description provided.