-
Notifications
You must be signed in to change notification settings - Fork 446
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
Enable securityContext override for all Gloo Edge deployments #8455
Comments
The override with This means that single properties define like this:
don't take effect anymore, so we have to copy/paste the whole section for each customer like this:
Because we have quite some customers we need to ask each what values they use, then render it for them and tell them what to put in there which is a lot of support effort for us for a simple feature that should be standard. So, yes there is a workaround but not a maintainable one. |
Hi, our customer is also asking to provide these values, not only for extauth deployment, but also for observability |
We would also need a possibility to set those properties for all gloo deployment resources and their containers. This is necessary for properly enabling pod security standards for the whole gloo deployment. |
Decided we need to have this for all our Gloo Edge deployments. Updated ticket title and scope. |
Duplicate of #8864. Closing this one. |
Version
1.14.x (latest stable)
Is your feature request related to a problem? Please describe.
I cannot override securityContext of the container unless I use kubeResourceOverride and for that I need to override the whole container definition.
Describe the solution you'd like
I would like to have a solution like you implemented for gloo or gateway-proxy pods where I could do:
gloo-ee: gloo: gloo: deployment: glooContainerSecurityContext: allowPrivilegeEscalation: false readOnlyRootFilesystem: true runAsNonRoot: true runAsUser: 10101 capabilities: drop: - ALL seccompProfile: type: RuntimeDefault
Describe alternatives you've considered
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: