Postgresql Cluster Pods getting "Readiness probe failed:" & "Liveness probe failed: " Error

General Discussions
1

Asking for help? Comment out what you need so we can get more information to help you!

Cluster information:

Kubernetes version: v1.21.12
Cloud being used: (put bare-metal if not on a public cloud) bare-metal
Installation method:
Host OS: CentOS Linux release 7.9.2009 (Core)
CNI and version: calico v3.22.2, flannel v0.17.0
CRI and version:

Hi Team,

I am not sure if this is the right place to raise a problem which I am facing.

I was trying to create an PostgreSQL cluster using the crunchydata operator. and I was able to install the operator successfully. but when i try to create an postgresql cluster i am getting below error.

“Readiness probe failed: Get “https://10.244.96.114:8008/readiness”: dial tcp 10.244.96.114:8008: connect: connection refused”

“Back-off restarting failed container”

Liveness probe failed: Get “https://10.244.96.114:8008/liveness”: dial tcp 10.244.96.114:8008: connect: connection refused

image

Below is my Postgres.yaml file .

apiVersion: postgres-operator.crunchydata.com/v1beta1
kind: PostgresCluster
metadata:
name: hippo
spec:
image: registry.developers.crunchydata.com/crunchydata/crunchy-postgres:ubi8-14.2-1
postgresVersion: 14
instances:
- name: instance1
dataVolumeClaimSpec:
accessModes:
- “ReadWriteOnce”
storageClassName: “openebs”
resources:
requests:
storage: 1Gi
backups:
pgbackrest:
image: registry.developers.crunchydata.com/crunchydata/crunchy-pgbackrest:ubi8-2.38-0
repos:
- name: repo1
volume:
volumeClaimSpec:
accessModes:
- “ReadWriteOnce”
storageClassName: “openebs”
resources:
requests:
storage: 1Gi
Regards,
Sameer Malve