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
Describe purpose and issues with openshift.io/run-level label on namespaces #303
Comments
Some breadcrumbs to the code would be useful too - e.g. the list of admission plugins that are skipped at run-level 1 |
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
Rotten issues close after 30d of inactivity. Reopen the issue by commenting /close |
@openshift-bot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
From Mark Cooper:
|
Next step would be to ask around for more information (say the API server team) and add some details to openshift/enhancements/CONVENTIONS.md |
Rotten issues close after 30d of inactivity. Reopen the issue by commenting /close |
@openshift-bot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Rotten issues close after 30d of inactivity. Reopen the issue by commenting /close |
@openshift-bot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Good to leave closed, PR complete #805 and additionally blog released: https://cloud.redhat.com/blog/exactly-what-are-openshift-runlevels-and-should-you-really-use-them |
In e.g. openshift/machine-api-operator#496 we stopped labeling some namespaces with
openshift.io/run-level: "1"
because those components "should follow normal admission control rules for a cluster".Some of the background on the purpose of this label and why it should generally be avoided is described in bz #1805488 and should be captured as a doc here.
The text was updated successfully, but these errors were encountered: