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
@tatsuhiro-t@balboah@weitzj
This is not exactly an issue instead I am looking for some solution for my requirement:
We have enabled the Pod Security Policy(PSP) in the cluster and due to the unprivileged PSP, the nghttpx-controller is forced to run as non-root user.
"securityContext":
{
"runAsUser": 65534,
"fsGroup": 65534
}
container creation failed with the error: mkdir etc/nghttpx permission denied.
Added the config "--nghttpx-conf-dir=/tmp" to use the tmp folder instead of etc/nghttpx. With this change the nghttpxx controller pod creation was successful.
When I tried creating the ingress service, service creation is failing and the error is: failed to write TLS private key: open /tmp/tls/nghttpx139340113: permission denied
Please note that everything works perfectly fine when it is assigned to privileged pod security policy and run as the root user
The text was updated successfully, but these errors were encountered:
@tatsuhiro-t @balboah @weitzj
This is not exactly an issue instead I am looking for some solution for my requirement:
We have enabled the
Pod Security Policy
(PSP) in the cluster and due to the unprivileged PSP, thenghttpx-controller
is forced to run asnon-root
user."securityContext":
{
"runAsUser": 65534,
"fsGroup": 65534
}
container creation failed with the error: mkdir
etc/nghttpx
permission denied.Added the config
"--nghttpx-conf-dir=/tmp"
to use thetmp
folder instead ofetc/nghttpx
. With this change the nghttpxx controller pod creation was successful.When I tried creating the ingress service, service creation is failing and the error is:
failed to write TLS private key: open /tmp/tls/nghttpx139340113: permission denied
Please note that everything works perfectly fine when it is assigned to privileged pod security policy and run as the root user
The text was updated successfully, but these errors were encountered: