One node cluster hangs in waiting state

zalando / postgres-operator

Postgres operator creates and manages PostgreSQL clusters running in Kubernetes

https://postgres-operator.readthedocs.io/

MIT License

4.35k stars 980 forks source link

One node cluster hangs in waiting state #1628

Open eskornev opened 3 years ago

eskornev commented 3 years ago

Which image of the operator are you using? registry.opensource.zalan.do/acid/postgres-operator:v1.6.2
Where do you run it - cloud or metal? Kubernetes or OpenShift? minikube
Are you running Postgres Operator in production? no
Type of issue? kind of bug

When originating one node cluster it's often ends up in waiting state - cluster pod says "waiting for leader to bootstrap". Deleting pods or upscaling cluster does not help. How can I resolve this state?

FxKu commented 3 years ago

Consider maybe updating to the most recent operator and spilo/patroni version. "originating" = "creating"? Are your resources maybe configured too high for minikube? Check the states of statefulset and database pod with kubectl describe.

eskornev commented 3 years ago

Thanks for reply! Upgrade is on its way! While testing I saw that renaming cluster and originating new with new name helps, cluster fires up successfully. Where can I check information about old clusters in kubectl or etcd?

FxKu commented 3 years ago

Old clusters? Not getting what you're asking here...

eskornev commented 3 years ago

Oh sorry "old" is that was deleted by "kubectl delete pg". When I install and remove helm release - I also remove cluster, with secrets and PVC altogether.