You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 12, 2023. It is now read-only.
Organisations usually come up with some best practices for monitoring and managing pods. A new policy could enforce a configurable list of labels to be mandatory to run a pod in the environment.
For example all pods should have an app label.
The policies.Config would need to be extended with a new field.
While this issue is for pods only it makes sense to think about enforcing labels for other components as well.
Another extension could be enforcing annotations on a type. For example kubernetes.io/ingress.class must not be empty for an ingress on a multi ingress-controller environment.
The text was updated successfully, but these errors were encountered:
👋 The k-rail project has been deprecated and is no longer under active development. We recommend taking a look at OPA Gatekeeper to see if it might meet your needs going forward.
Thanks for your contribution(s) to the project!
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Organisations usually come up with some best practices for monitoring and managing pods. A new policy could enforce a configurable list of labels to be mandatory to run a pod in the environment.
For example all pods should have an
app
label.The policies.Config would need to be extended with a new field.
🤔 Extensions
pods
only it makes sense to think about enforcing labels for other components as well.annotations
on a type. For examplekubernetes.io/ingress.class
must not be empty for an ingress on a multi ingress-controller environment.The text was updated successfully, but these errors were encountered: