-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Allow per-namespace annotations-risk-level #12639
Comments
This issue is currently awaiting triage. If Ingress contributors determines this is a relevant issue, they will accept it by applying the The 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-sigs/prow repository. |
Other usecases (for kube-apiserver): nginx.ingress.kubernetes.io/server-snippet: |
client_header_buffer_size 40k;
large_client_header_buffers 4 40k; |
We lowered the annotation risk level to Anyway: We won't implement a feature like this as we're currently looking forward to our Gateway API implementation. |
We are using multi-tenant clusters, and will probably move to another Gateway API implementation than ingate, but a few features are still missing in Gateway API specs. We'll use Gatekeeper to check ingress-nginx annotations. |
Raising annotations-risk-level to High is good, but we need a way to add exceptions for specific namespaces that we now are using safe parameters.
For example, we use this for MinIO:
Proposed change: add a new option in ConfigMap
annotations-risk-level-excluded-namespaces
containing a space-separed list of namespaces whereannotations-risk-level
is set to Critical.The text was updated successfully, but these errors were encountered: