I am creating percona postgres operator and cluster is showing initializing from long time

PostgreSQL Percona Operator for PostgreSQL
1

[root@master-sk percona-postgresql-operator]# kubectl get pg -n postgres-operator
NAME ENDPOINT STATUS POSTGRES PGBOUNCER AGE
cluster1 cluster1-pgbouncer.postgres-operator.svc initializing 3 18m

I am creating percona postgres operator and cluster is showing initializing from long time .

below is the logs mention instance pod.

[root@master-sk percona-postgresql-operator]# kubectl logs cluster1-instance1-jcfg-0 -n postgres-operator
Defaulted container “database” out of: database, replication-cert-copy, pgbackrest, pgbackrest-config, postgres-startup (init), nss-wrapper-init (init)

Below are the running pods related to operator.

[root@master-sk percona-postgresql-operator]# kubectl get pods -n postgres-operator
NAME READY STATUS RESTARTS AGE
cluster1-instance1-7k2l-0 0/4 Pending 0 16m
cluster1-instance1-jcfg-0 0/4 Pending 0 16m
cluster1-instance1-nxxx-0 0/4 Pending 0 16m
cluster1-pgbouncer-8567f9fc98-ddpgv 2/2 Running 0 16m
cluster1-pgbouncer-8567f9fc98-lmwhr 2/2 Running 0 16m
cluster1-pgbouncer-8567f9fc98-s9qs6 2/2 Running 0 16m
cluster1-repo-host-0 0/2 Pending 0 16m
percona-postgresql-operator-6f96ffd8d4-47hxh 1/1 Running 0 16m

2

Hey @aws_learning ,

seems your cluster pods are in pending state. You can describe them and see the reason for that. Usually it indicates that you don’t have enough resources in your k8s cluster.

Can you run kubectl describe pod cluster1-instance1-7k2l-0 ?