postgres DB cluster pod initiation not happening #2208
vponnathota
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
till postgres operator its all good but postgres DB cluster initiation is not happening
I have dynamic NFS storage is ready and storageclass provided in complete-manifest-postgres.yaml but still nothing progress...DB cluster pod initiation is not happening. please advise here.
k get all -n zalando
NAME READY STATUS RESTARTS AGE
pod/postgres-operator-65b9dc4789-xmgfc 1/1 Running 0 23m
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/postgres-operator ClusterIP xxxxx 8080/TCP 3d1h
NAME READY UP-TO-DATE AVAILABLE AGE
deployment.apps/postgres-operator 1/1 1 1 45m
NAME DESIRED CURRENT READY AGE
replicaset.apps/postgres-operator-5c4f4cbcd 0 0 0 45m
replicaset.apps/postgres-operator-65b9dcxxxx 1 1 1 23m
NAME IMAGE CLUSTER-LABEL SERVICE-ACCOUNT MIN-INSTANCES AGE
operatorconfiguration.acid.zalan.do/postgresql-operator-default-configuration ghcr.io/zalando/spilo-15:2.1-p9 cluster-name postgres-pod -1 3d1h
NAME TEAM VERSION PODS VOLUME CPU-REQUEST MEMORY-REQUEST AGE STATUS
postgresql.acid.zalan.do/acid-test-cluster acid 14 2 1Gi 10m 100Mi 19m
postgresql.acid.zalan.do/postgresql-test-cluster postgresql 14 1 2Gi 2d1h
k get pods -n zalando
NAME READY STATUS RESTARTS AGE
postgres-operator-65b9dc4789-xmgfc 1/1 Running 0 27m
k get sc -n zalando
NAME PROVISIONER RECLAIMPOLICY VOLUMEBINDINGMODE ALLOWVOLUMEEXPANSION AGE
managed-nfs-storage example.com/nfs Delete Immediate false 236d
Beta Was this translation helpful? Give feedback.
All reactions