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

Add kube-system as an immortal namespace #17808

Closed
wants to merge 1 commit into from
Closed

Add kube-system as an immortal namespace #17808

wants to merge 1 commit into from

Conversation

liggitt
Copy link
Contributor

@liggitt liggitt commented Dec 14, 2017

No description provided.

@openshift-ci-robot
Copy link

[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 /approve in a comment
You can cancel your approval by writing /approve cancel in a comment

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 14, 2017
@openshift-ci-robot openshift-ci-robot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Dec 14, 2017
@liggitt liggitt added this to the 3.9.0 milestone Dec 19, 2017
@@ -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)
Copy link
Contributor

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.

Copy link
Contributor Author

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

Copy link
Contributor Author

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

@deads2k
Copy link
Contributor

deads2k commented Dec 21, 2017

opened #17914 as an alternative in head.

@liggitt
Copy link
Contributor Author

liggitt commented Jan 2, 2018

closing in favor of #17914

@liggitt liggitt closed this Jan 2, 2018
openshift-merge-robot added a commit that referenced this pull request Jan 10, 2018
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.
openshift-publish-robot pushed a commit to openshift/kubernetes that referenced this pull request Jan 24, 2018
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
openshift-publish-robot pushed a commit to openshift/kubernetes that referenced this pull request Jan 25, 2018
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
openshift-publish-robot pushed a commit to openshift/kubernetes that referenced this pull request Feb 27, 2018
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
openshift-publish-robot pushed a commit to openshift/kubernetes-apiserver that referenced this pull request Feb 28, 2018
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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants