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
Add default pod and container security context settings.
Background
At the moment, the operator creates a deployment without any security context settings, so will use the cluster defaults. SpiceDB is relatively low risk because it's not an external-facing service, but it would still be helpful to add some more restrictive defaults, because some clusters have admission controllers that enforce more restrictive policies (tools like Kyverno, OPA Gatekeeper, or OpenShift)
The deployment currently looks like this in our cluster (some irrelevant data removed to highlight the securityContext):
Adding some default pod and container security context settings would be useful:
runAsNonRoot
readOnlyRootFilesystem
Drop capabilities
Use default seccomp profile
Workaround
Users can apply this manually using patches, but it's preferable to have hardened defaults, especially because the SpiceDB maintainers have a better sense of the constraints that would work for you.
The text was updated successfully, but these errors were encountered:
jawnsy
changed the title
Default security context settings
Default security context settings for SpiceDB Clusters
Aug 16, 2023
Summary
Add default pod and container security context settings.
Background
At the moment, the operator creates a deployment without any security context settings, so will use the cluster defaults. SpiceDB is relatively low risk because it's not an external-facing service, but it would still be helpful to add some more restrictive defaults, because some clusters have admission controllers that enforce more restrictive policies (tools like Kyverno, OPA Gatekeeper, or OpenShift)
The deployment currently looks like this in our cluster (some irrelevant data removed to highlight the
securityContext
):Adding some default pod and container security context settings would be useful:
Workaround
Users can apply this manually using patches, but it's preferable to have hardened defaults, especially because the SpiceDB maintainers have a better sense of the constraints that would work for you.
The text was updated successfully, but these errors were encountered: