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
These customizations are required because some environments, such as OpenShift, or clusters that enforce restrictive policies using tools like Open Policy Agent Gatekeeper or Kyverno, will not be able to install retool otherwise.
Current behavior
The chart looks for a
securityContext.enabled
setting, which sets a default security context:retool-helm/templates/deployment_backend.yaml
Lines 219 to 223 in 1e06cee
However, the default values file implies that other securityContext settings can be set on the pod, but in fact, those values are ignored:
retool-helm/values.yaml
Lines 271 to 276 in 1e06cee
Desired behavior
We should be able to configure all of the settings defined in the PodSecurityContext API: https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.24/#podsecuritycontext-v1-core
I would also expect that we can configure all the SecurityContext settings for the primary retool container
These customizations are required because some environments, such as OpenShift, or clusters that enforce restrictive policies using tools like Open Policy Agent Gatekeeper or Kyverno, will not be able to install retool otherwise.
Steps to reproduce
You can see this by running a command like:
You will see output like the following:
It's not possible to override the
runAsUser
, to addrunAsGroup
information, or to setrunAsNonRoot: true
Other information
Here's my chart version information:
The text was updated successfully, but these errors were encountered: