Open kper3360 opened 2 weeks ago
Hi!
Could you add more details on the PVC provider you are using? It may have incompatibilities with fsGroup
I use EFS CSI Provisioner
Could you try with the volume permissions init container? volumePermissions.enabled=true
?
Could you try with the volume permissions init container?
volumePermissions.enabled=true
?
I tried it. But it didn't work
Could you deploy the chart with diagnosticMode.enabled=true
, enter the container with kubectl exec and check the permissions on the volume folder?
@javsalgar I have same problem.
The default user id of EFS is 50011, so I tried below config but it doesn't works.
volumePermissions:
enabled: true
containerSecurityContext:
runAsUser: 50011
runAsGroup: 50011
runAsNonRoot: false
Even with that user/group, you are unable to perform a touch command inside the container? What error does it show?
Name and Version
/bitnami/postgresql/16.4.0-debian-12-r5
What architecture are you using?
None
What steps will reproduce the bug?
Environment- AWS EKS V 1.28
Are you using any custom parameters or values?
no
What is the expected behavior?
No response
What do you see instead?
After I installed the Helm chart the the pod went to crashloopbackoff status.
my-postgresql-0 0/1 CrashLoopBackOff 10 (80s ago) 28m
Additional information
No response