InitDB not initializing dueto mkdir: cannot create directory ‘/home/postgres/pgdata/pgroot’: Read-only file system

Please, answer some short questions which should help us to understand your problem / question better?

• Which image of the operator are you using? registry.opensource.zalan.do/acid/spilo-14:2.1-p6
• **Where do you run it - cloud or metal? Kubernetes on a VM [1 master, 2 worker nodes]
• Are you running Postgres Operator in production? [no]
• Type of issue? [Bug report]

I am performing a manuall installation of postgres cluster based on Zalando quick start guide using URL https://github.com/zalando/postgres-operator/blob/master/docs/quickstart.md

FYI - I have used PVC claimed using Trident.

I have followed all the steps but the pod is not in ready status.

NAME READY STATUS RESTARTS AGE
acid-minimal-cluster-0 0/1 Running 0 120m

The container logs shows the following error

kubectl logs acid-minimal-cluster-0 -c postgres
mkdir: cannot create directory ‘/home/postgres/pgdata/pgroot’: Read-only file system
mkdir: cannot create directory ‘/home/postgres/pgdata/pgroot’: Read-only file system
touch: cannot touch '/home/postgres/pgdata/pgroot/pg_log/postgresql-0.csv': No such file or directory

Please find below the Postgres operator status

kubectl get pod -l name=postgres-operator
NAME READY STATUS RESTARTS AGE
postgres-operator-6b8c5c9656-4bl26 1/1 Running 1 (3h30m ago) 3h30m

kubectl get postgresql
NAME TEAM VERSION PODS VOLUME CPU-REQUEST MEMORY-REQUEST AGE STATUS
acid-minimal-cluster acid 14 2 1Gi 152m SyncFailed

Could you please help on this?

Start with docs/quickstart.md and the reported kubectl logs for acid-minimal-cluster-0. Check how the Trident PVC is mounted and why /home/postgres/pgdata is read-only, then verify the pod becomes ready and the PostgreSQL resource leaves SyncFailed.