In our org, we have rather strict policies regarding the pod security context.
To enable TLS, I see that the chart adds an init container that does some chmod'ing of certificate files. For that to happen, the securityContext of the init container is currently:
Name and Version
bitnami/postgresql-ha
What is the problem this feature will solve?
In our org, we have rather strict policies regarding the pod security context. To enable TLS, I see that the chart adds an init container that does some chmod'ing of certificate files. For that to happen, the securityContext of the init container is currently:
In our org, we are not allowed to choose user/group 0 and cannot run containers as root either. My org wants:
But this leads to
What is the feature you are proposing to solve the problem?
Why not just directly mount the certificates with mode 0600?
I'm curious about the choice for the initContainer that does: