Hi, if you are using EFS as the shared storage then you may want to try the suggestion from https://devops.stackexchange.com/questions/13939/how-to-allow-a-non-root-user-to-write-to-a-mounted-efs-in-eks/13944#13944 to use EFS access points?

I found and worked around the issue.

A post on one of the SM sites mentioned that fsGroup and securityContext in Kubernetes only works for emptyDir volume mounts. HostPath persistent volumes are created as root with 0600 for chmod permissions, and most implementations of Pod Security Policies, and apparently the later Pod Security Admission, ignore fsGroup changes on such PVs (chown and chmod just no-op and ignore the request).

The workaround is to remove the hostPath definition that created the pod folder /mnt/data from the PV resource. That let me configure the database and get to the home screen. Connecting to the pod showed the permissions on the mounted PV were correct.

Great to hear that it's working now. Would you mind sharing the sample YAML configuration for this? It would be interesting to know what the actual configuration is like.