-
Notifications
You must be signed in to change notification settings - Fork 645
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
K8S securityContext / runAsNonRoot #383
Comments
Im using the 0.10.0 tag, and my containers run like this:
So the only one that has to be changed is the redis one. BTW, im having the same problem with the rsyslog file.. Also tested 0.9.0 and same error. Maybe we should rise a different issue. |
Any idea if this would be part of a future release, to avoid manual changes to the deployment YAML? |
I'm using the postgres and redis image from bitnami as a workaround since they run as non-root. From my awx-demo.yaml file: spec: |
We have a policy of not running any containers as root.
By default it looks like all awx and redis containers is starting as root and will fail/not start in our cluster do to default PSP in cluster.
If i manually update deployment manifest with SecurityContext for container is looks like its working...
Running as root is general not a recommended practice.
I also had to manually create file in container awx-task.:
log-output before fix.
Somehow this file was not generated.
What about adding a SecurityContext or a general Spec in the crds to override this?
Or sync dockerimage + deployment with correct non-root user to allow read-write where its needed.
The text was updated successfully, but these errors were encountered: