khalifaould

As part of our resilience tests we have a cluster with 3 master nodes on which we launched a crunchydata cluster with 3 replicas. The list of pods  We...

``` Cluster Config `apiVersion: postgres-operator.crunchydata.com/v1beta1 kind: PostgresCluster metadata: name: db-cluster namespace: namespace spec: image: registry.developers.crunchydata.com/crunchydata/crunchy-postgres:centos8-13.4-1 postgresVersion: 13 instances: - name: instance1 replicas: 3 dataVolumeClaimSpec: accessModes: - "ReadWriteOnce" resources: requests: storage:...

The pod is not reprogrammed on one of the other nodes and that's the problem !! Looks like there is an affinity with the node it first launched on

Platform: Rancher K3S Platform Version: v1.19.7+k3s1 PGO Image Tag: ubi8-5.0.3-0 Postgres Version : 13 Storage: Default( local-path) The dai-prod-db-repo-host-0 pod is not status pending but Terminating. kubectl describe pod dai-prod-db-repo-host-0...