seqr container in CrashLoopBackOff — "Failed to connect to localhost port 8000: Connection refused"

[ysayyed11]

Describe the issue

We deployed seqr via Helm (seqr-platform chart) on a local kind cluster, and the seqr pod keeps going into CrashLoopBackOff.
The startup probe repeatedly fails with the message:
curl: (7) Failed to connect to localhost port 8000: Connection refused

jgyi,The deployment uses NFS-backed storage for persistent volumes.
Since the seqr Helm chart expects data to be available under /var/seqr, we’ve created a symlink to point that path to the mounted NFS share.

Pod description

kubectl describe pod seqr-postgresql-0
Name: seqr-postgresql-0
Namespace: default
Priority: 0
Service Account: seqr-postgresql
Node: kind-control-plane/172.18.0.2
Start Time: Mon, 20 Oct 2025 12:53:08 +0300
Labels: app.kubernetes.io/component=primary
app.kubernetes.io/instance=sidra-seqr
app.kubernetes.io/managed-by=Helm
app.kubernetes.io/name=postgresql
app.kubernetes.io/version=16.4.0
apps.kubernetes.io/pod-index=0
controller-revision-hash=seqr-postgresql-65868cbcf9
helm.sh/chart=postgresql-15.5.31
statefulset.kubernetes.io/pod-name=seqr-postgresql-0
Annotations:
Status: Running
IP: 10.244.0.182
IPs:
IP: 10.244.0.182
Controlled By: StatefulSet/seqr-postgresql
Init Containers:
seqr-postgresql-init-chmod-data:
Container ID: containerd://cfb26f6cbe6fa3c1c7bdb13e8f5e9bc13f842f55f19388aae9bb84124fe25445
Image: bitnamilegacy/os-shell
Image ID: docker.io/bitnamilegacy/os-shell@sha256:8f020b42160f0a0b66d8d3f2fdc80a27563b585021267dd868263704aef2dfeb
Port:
Host Port:
SeccompProfile: RuntimeDefault
Command:
/bin/sh
-ec
mkdir -p /var/seqr/postgresql-data
chown -R id -u:id -G | cut -d " " -f2 /var/seqr/postgresql-data

State:          Terminated
  Reason:       Completed
  Exit Code:    0
  Started:      Mon, 20 Oct 2025 12:57:16 +0300
  Finished:     Mon, 20 Oct 2025 12:57:18 +0300
Ready:          True
Restart Count:  0
Environment:    <none>
Mounts:
  /var/seqr from data (rw)

Containers:
postgresql:
Container ID: containerd://806dba876fea271523d3587a000f1174e626413094e0ab99dc51dae9ffee8db1
Image: docker.io/bitnamilegacy/postgresql:12.19.0-debian-12-r9
Image ID: docker.io/bitnamilegacy/postgresql@sha256:dc2f9d41425f0a990fef9979f460f3f589cca48a21b53914663d4912d13dd9e4
Port: 5432/TCP
Host Port: 0/TCP
SeccompProfile: RuntimeDefault
State: Running
Started: Mon, 20 Oct 2025 13:24:05 +0300
Last State: Terminated
Reason: Error
Exit Code: 137
Started: Mon, 20 Oct 2025 13:20:45 +0300
Finished: Mon, 20 Oct 2025 13:24:05 +0300
Ready: False
Restart Count: 8
Limits:
memory: 2Gi
Requests:
memory: 2Gi
Liveness: exec [/bin/sh -c exec pg_isready -U "postgres" -h 127.0.0.1 -p 5432] delay=30s timeout=5s period=10s #success=1 #failure=6
Readiness: exec [/bin/sh -c -e exec pg_isready -U "postgres" -h 127.0.0.1 -p 5432
] delay=5s timeout=5s period=10s #success=1 #failure=6
Startup: exec [/bin/sh -c exec pg_isready -U "postgres" -h 127.0.0.1 -p 5432] delay=30s timeout=1s period=10s #success=1 #failure=15
Environment:
BITNAMI_DEBUG: false
POSTGRESQL_PORT_NUMBER: 5432
POSTGRESQL_VOLUME_DIR: /var/seqr
PGDATA: /var/seqr/postgresql-data
POSTGRES_PASSWORD: <set to the key 'password' in secret 'postgres-secrets'> Optional: false
POSTGRESQL_ENABLE_LDAP: no
POSTGRESQL_ENABLE_TLS: no
POSTGRESQL_LOG_HOSTNAME: false
POSTGRESQL_LOG_CONNECTIONS: false
POSTGRESQL_LOG_DISCONNECTIONS: false
POSTGRESQL_PGAUDIT_LOG_CATALOG: off
POSTGRESQL_CLIENT_MIN_MESSAGES: error
POSTGRESQL_SHARED_PRELOAD_LIBRARIES: pgaudit
Mounts:
/dev/shm from dshm (rw)
/docker-entrypoint-initdb.d/ from custom-init-scripts (rw)
/opt/bitnami/postgresql/conf from empty-dir (rw,path="app-conf-dir")
/opt/bitnami/postgresql/tmp from empty-dir (rw,path="app-tmp-dir")
/tmp from empty-dir (rw,path="tmp-dir")
/var/seqr from data (rw)
Conditions:
Type Status
PodReadyToStartContainers True
Initialized True
Ready False
ContainersReady False
PodScheduled True
Volumes:
empty-dir:
Type: EmptyDir (a temporary directory that shares a pod's lifetime)
Medium:
SizeLimit:
custom-init-scripts:
Type: ConfigMap (a volume populated by a ConfigMap)
Name: seqr-postgresql-init-scripts
Optional: false
dshm:
Type: EmptyDir (a temporary directory that shares a pod's lifetime)
Medium: Memory
SizeLimit:
data:
Type: PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
ClaimName: seqr-platform-pvc
ReadOnly: false
QoS Class: Burstable
Node-Selectors:
Tolerations: node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
Type Reason Age From Message

---

Warning FailedScheduling 34m default-scheduler 0/1 nodes are available: pod has unbound immediate PersistentVolumeClaims. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling.
Normal Scheduled 34m default-scheduler Successfully assigned default/seqr-postgresql-0 to kind-control-plane
Normal Pulled 30m kubelet Container image "bitnamilegacy/os-shell" already present on machine
Normal Created 30m kubelet Created container: seqr-postgresql-init-chmod-data
Normal Started 30m kubelet Started container seqr-postgresql-init-chmod-data
Normal Started 13m (x6 over 30m) kubelet Started container postgresql
Normal Pulled 10m (x7 over 30m) kubelet Container image "docker.io/bitnamilegacy/postgresql:12.19.0-debian-12-r9" already present on machine
Normal Created 10m (x7 over 30m) kubelet Created container: postgresql
Warning Unhealthy 4m20s (x117 over 29m) kubelet Startup probe failed: 127.0.0.1:5432 - rejecting connections
Normal Killing 3m50s (x8 over 27m) kubelet Container postgresql failed startup probe, will be restarted
[root@seqr-prod seqr]# kubectl describe pod seqr-b45cbdfc8-6phm
Name: seqr-b45cbdfc8-6phmg
Namespace: default
Priority: 0
Service Account: seqr
Node: kind-control-plane/172.18.0.2
Start Time: Mon, 20 Oct 2025 12:53:08 +0300
Labels: app.kubernetes.io/instance=sidra-seqr
app.kubernetes.io/managed-by=Helm
app.kubernetes.io/name=seqr
app.kubernetes.io/part-of=seqr-platform
app.kubernetes.io/version=b6fdd9c208f50f2102c1b650db6c41b002fbdaf5
helm.sh/chart=seqr-3.11.0
name=seqr
pod-template-hash=b45cbdfc8
Annotations: checksum/config: db35e292491b1d03ff14849eed9fef5e58a0f9e55697ac0fe0a5fa936e100d67
Status: Running
IP: 10.244.0.179
IPs:
IP: 10.244.0.179
Controlled By: ReplicaSet/seqr-b45cbdfc8
Init Containers:
mkdir-loading-datasets:
Container ID: containerd://8215abfddb50a240debddf70a2d5be9933a7be4170ab70f8fd0ca6817f2eb31d
Image: busybox:1.35
Image ID: docker.io/library/busybox@sha256:98ad9d1a2be345201bb0709b0d38655eb1b370145c7d94ca1fe9c421f76e245a
Port:
Host Port:
Command:
/bin/mkdir
-p
/var/seqr/seqr-loading-temp
State: Terminated
Reason: Completed
Exit Code: 0
Started: Mon, 20 Oct 2025 12:57:22 +0300
Finished: Mon, 20 Oct 2025 12:57:22 +0300
Ready: True
Restart Count: 0
Environment:
Mounts:
/var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-ltgxb (ro)
/var/seqr from seqr-datasets (rw)
Containers:
seqr:
Container ID: containerd://4438717914c395e607c16e3997e5da830d0ca180e3d298200870d31ef051cd9d
Image: gcr.io/seqr-project/seqr:b6fdd9c208f50f2102c1b650db6c41b002fbdaf5
Image ID: gcr.io/seqr-project/seqr@sha256:12bbacffcf0f9671e20dc81c4bc6a9c9e15b609b63075f126e63e56770d34503
Port: 8000/TCP
Host Port: 0/TCP
State: Waiting
Reason: CrashLoopBackOff
Last State: Terminated
Reason: Error
Exit Code: 1
Started: Mon, 20 Oct 2025 13:24:02 +0300
Finished: Mon, 20 Oct 2025 13:26:00 +0300
Ready: False
Restart Count: 8
Liveness: exec [/bin/bash -c /readiness_probe] delay=0s timeout=1s period=10s #success=1 #failure=3
Readiness: exec [/bin/bash -c /readiness_probe] delay=0s timeout=1s period=10s #success=1 #failure=3
Startup: exec [/bin/bash -c /readiness_probe] delay=0s timeout=1s period=15s #success=1 #failure=60
Environment Variables from:
seqr ConfigMap Optional: false
Environment:
POSTGRES_PASSWORD: <set to the key 'password' in secret 'postgres-secrets'> Optional: false
DJANGO_KEY: <set to the key 'django_key' in secret 'seqr-secrets'> Optional: false
CLICKHOUSE_READER_PASSWORD: <set to the key 'reader_password' in secret 'clickhouse-secrets'> Optional: true
CLICKHOUSE_WRITER_PASSWORD: <set to the key 'writer_password' in secret 'clickhouse-secrets'> Optional: true
Mounts:
/var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-ltgxb (ro)
/var/seqr from seqr-datasets (rw)
Conditions:
Type Status
PodReadyToStartContainers True
Initialized True
Ready False
ContainersReady False
PodScheduled True
Volumes:
seqr-datasets:
Type: PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
ClaimName: seqr-platform-pvc
ReadOnly: false
kube-api-access-ltgxb:
Type: Projected (a volume that contains injected data from multiple sources)
TokenExpirationSeconds: 3607
ConfigMapName: kube-root-ca.crt
Optional: false
DownwardAPI: true
QoS Class: BestEffort
Node-Selectors:
Tolerations: node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
Type Reason Age From Message

---

Normal Scheduled 34m default-scheduler Successfully assigned default/seqr-b45cbdfc8-6phmg to kind-control-plane
Warning FailedScheduling 34m default-scheduler 0/1 nodes are available: pod has unbound immediate PersistentVolumeClaims. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling.
Normal Pulling 30m kubelet Pulling image "busybox:1.35"
Normal Pulled 30m kubelet Successfully pulled image "busybox:1.35" in 2.176s (5.713s including waiting). Image size: 2159953 bytes.
Normal Created 30m kubelet Created container: mkdir-loading-datasets
Normal Started 30m kubelet Started container mkdir-loading-datasets
Normal Pulled 30m kubelet Successfully pulled image "gcr.io/seqr-project/seqr:b6fdd9c208f50f2102c1b650db6c41b002fbdaf5" in 1.611s (4.349s including waiting). Image size: 417115309 bytes.
Normal Pulled 28m kubelet Successfully pulled image "gcr.io/seqr-project/seqr:b6fdd9c208f50f2102c1b650db6c41b002fbdaf5" in 1.509s (1.509s including waiting). Image size: 417115309 bytes.
Normal Pulled 25m kubelet Successfully pulled image "gcr.io/seqr-project/seqr:b6fdd9c208f50f2102c1b650db6c41b002fbdaf5" in 1.579s (1.579s including waiting). Image size: 417115309 bytes.
Normal Pulled 23m kubelet Successfully pulled image "gcr.io/seqr-project/seqr:b6fdd9c208f50f2102c1b650db6c41b002fbdaf5" in 1.745s (1.745s including waiting). Image size: 417115309 bytes.
Normal Pulled 20m kubelet Successfully pulled image "gcr.io/seqr-project/seqr:b6fdd9c208f50f2102c1b650db6c41b002fbdaf5" in 1.486s (1.486s including waiting). Image size: 417115309 bytes.
Normal Started 20m (x5 over 30m) kubelet Started container seqr
Normal Created 17m (x6 over 30m) kubelet Created container: seqr
Normal Pulled 17m kubelet Successfully pulled image "gcr.io/seqr-project/seqr:b6fdd9c208f50f2102c1b650db6c41b002fbdaf5" in 1.52s (1.52s including waiting). Image size: 417115309 bytes.
Warning BackOff 9m48s (x38 over 26m) kubelet Back-off restarting failed container seqr in pod seqr-b45cbdfc8-6phmg_default(04bd3075-e82d-4996-a412-2befd7f27c9a)
Normal Pulling 5m13s (x8 over 30m) kubelet Pulling image "gcr.io/seqr-project/seqr:b6fdd9c208f50f2102c1b650db6c41b002fbdaf5"
Normal Pulled 5m12s kubelet Successfully pulled image "gcr.io/seqr-project/seqr:b6fdd9c208f50f2102c1b650db6c41b002fbdaf5" in 1.881s (1.881s including waiting). Image size: 417115309 bytes.
Warning Unhealthy 4m46s (x57 over 30m) kubelet Startup probe failed: % Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
\r 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0\r 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to localhost port 8000: Connection refused

[bpblanken]

I see

Normal Killing 3m50s (x8 over 27m) kubelet Container postgresql failed startup probe, will be restarted

and

Last State: Terminated
Reason: Error
Exit Code: 137

in the logs, which may indicate issues with postgres starting. I'd check to make sure you've correctly defined the postgres secret and that that service is coming up alright first before seqr itself.

[ysayyed11]

The secrets are correctly defined, and the other configurations are as per the suggestion.

kubectl get secrets -n default
NAME TYPE DATA AGE
clickhouse-secrets Opaque 3 35h
postgres-secrets Opaque 1 10m
seqr-clickhouse-init-db-secret Opaque 1 8h
seqr-secrets Opaque 1 10m
sh.helm.release.v1.sidra-seqr.v1 helm.sh/release.v1 1 8h

[bpblanken]

@ysayyed11 Are you able to describe the postgres pod and tail the logs to see why it's not starting?

One gotcha there is a file like /var/seqr/.user_scripts_initialized, which is written when postgres is initialized for the first time, and subsequent attempts may be blocked from initializing if there was a failure within the startup at a later point.

[ysayyed11]

No file /var/seqr/.user_scripts_initialized found in /var/seqr

the logs are as below:
kubectl describe pod seqr-postgresql-0
Name: seqr-postgresql-0
Namespace: default
Priority: 0
Service Account: seqr-postgresql
Node: kind-control-plane/172.18.0.2
Start Time: Mon, 20 Oct 2025 21:59:35 +0300
Labels: app.kubernetes.io/component=primary
app.kubernetes.io/instance=sidra-seqr
app.kubernetes.io/managed-by=Helm
app.kubernetes.io/name=postgresql
app.kubernetes.io/version=16.4.0
apps.kubernetes.io/pod-index=0
controller-revision-hash=seqr-postgresql-65868cbcf9
helm.sh/chart=postgresql-15.5.31
statefulset.kubernetes.io/pod-name=seqr-postgresql-0
Annotations:
Status: Running
IP: 10.244.0.102
IPs:
IP: 10.244.0.102
Controlled By: StatefulSet/seqr-postgresql
Init Containers:
seqr-postgresql-init-chmod-data:
Container ID: containerd://e51aab5eed9abd1567873fe1c8dfa0db5f8f83eb803fe1bedc28bdd975a2c8bd
Image: bitnamilegacy/os-shell
Image ID: docker.io/bitnamilegacy/os-shell@sha256:8f020b42160f0a0b66d8d3f2fdc80a27563b585021267dd868263704aef2dfeb
Port:
Host Port:
SeccompProfile: RuntimeDefault
Command:
/bin/sh
-ec
mkdir -p /var/seqr/postgresql-data
chown -R id -u:id -G | cut -d " " -f2 /var/seqr/postgresql-data

State:          Terminated
  Reason:       Completed
  Exit Code:    0
  Started:      Mon, 20 Oct 2025 21:59:36 +0300
  Finished:     Mon, 20 Oct 2025 21:59:38 +0300
Ready:          True
Restart Count:  0
Environment:    <none>
Mounts:
  /var/seqr from data (rw)

Containers:
postgresql:
Container ID: containerd://82fe795377dc7e84e1a2621a7a7abbd34f12e92dc361a28dc3be19f509e4ba43
Image: docker.io/bitnamilegacy/postgresql:12.19.0-debian-12-r9
Image ID: docker.io/bitnamilegacy/postgresql@sha256:dc2f9d41425f0a990fef9979f460f3f589cca48a21b53914663d4912d13dd9e4
Port: 5432/TCP
Host Port: 0/TCP
SeccompProfile: RuntimeDefault
State: Waiting
Reason: CrashLoopBackOff
Last State: Terminated
Reason: Error
Exit Code: 137
Started: Tue, 21 Oct 2025 13:16:56 +0300
Finished: Tue, 21 Oct 2025 13:20:26 +0300
Ready: False
Restart Count: 159
Limits:
memory: 2Gi
Requests:
memory: 2Gi
Liveness: exec [/bin/sh -c exec pg_isready -U "postgres" -h 127.0.0.1 -p 5432] delay=30s timeout=5s period=10s #success=1 #failure=6
Readiness: exec [/bin/sh -c -e exec pg_isready -U "postgres" -h 127.0.0.1 -p 5432
] delay=5s timeout=5s period=10s #success=1 #failure=6
Startup: exec [/bin/sh -c exec pg_isready -U "postgres" -h 127.0.0.1 -p 5432] delay=30s timeout=1s period=10s #success=1 #failure=15
Environment:
BITNAMI_DEBUG: false
POSTGRESQL_PORT_NUMBER: 5432
POSTGRESQL_VOLUME_DIR: /var/seqr
PGDATA: /var/seqr/postgresql-data
POSTGRES_PASSWORD: <set to the key 'password' in secret 'postgres-secrets'> Optional: false
POSTGRESQL_ENABLE_LDAP: no
POSTGRESQL_ENABLE_TLS: no
POSTGRESQL_LOG_HOSTNAME: false
POSTGRESQL_LOG_CONNECTIONS: false
POSTGRESQL_LOG_DISCONNECTIONS: false
POSTGRESQL_PGAUDIT_LOG_CATALOG: off
POSTGRESQL_CLIENT_MIN_MESSAGES: error
POSTGRESQL_SHARED_PRELOAD_LIBRARIES: pgaudit
Mounts:
/dev/shm from dshm (rw)
/docker-entrypoint-initdb.d/ from custom-init-scripts (rw)
/opt/bitnami/postgresql/conf from empty-dir (rw,path="app-conf-dir")
/opt/bitnami/postgresql/tmp from empty-dir (rw,path="app-tmp-dir")
/tmp from empty-dir (rw,path="tmp-dir")
/var/seqr from data (rw)
Conditions:
Type Status
PodReadyToStartContainers True
Initialized True
Ready False
ContainersReady False
PodScheduled True
Volumes:
empty-dir:
Type: EmptyDir (a temporary directory that shares a pod's lifetime)
Medium:
SizeLimit:
custom-init-scripts:
Type: ConfigMap (a volume populated by a ConfigMap)
Name: seqr-postgresql-init-scripts
Optional: false
dshm:
Type: EmptyDir (a temporary directory that shares a pod's lifetime)
Medium: Memory
SizeLimit:
data:
Type: PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
ClaimName: seqr-platform-pvc
ReadOnly: false
QoS Class: Burstable
Node-Selectors:
Tolerations: node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
Type Reason Age From Message

---

Normal Created 40m (x153 over 15h) kubelet Created container: postgresql
Warning BackOff 11m (x2042 over 14h) kubelet Back-off restarting failed container postgresql in pod seqr-postgresql-0_default(93a106b0-4532-4708-978e-29db7613d552)
Normal Pulled 7m28s (x170 over 15h) kubelet Container image "docker.io/bitnamilegacy/postgresql:12.19.0-debian-12-r9" already present on machine
Warning Unhealthy 73s (x2114 over 15h) kubelet Startup probe failed: 127.0.0.1:5432 - no response
Normal Killing 63s (x141 over 15h) kubelet Container postgresql failed startup probe, will be restarted
[root@seqr-prod postgresql-data]# kubectl logs -f seqr-postgresql-0 -n default
Defaulted container "postgresql" out of: postgresql, seqr-postgresql-init-chmod-data (init)
postgresql 10:16:56.57 INFO ==>
postgresql 10:16:56.58 INFO ==> Welcome to the Bitnami postgresql container
postgresql 10:16:56.58 INFO ==> Subscribe to project updates by watching https://github.com/bitnami/containers
postgresql 10:16:56.58 INFO ==> Submit issues and feature requests at https://github.com/bitnami/containers/issues
postgresql 10:16:56.58 INFO ==> Upgrade to Tanzu Application Catalog for production environments to access custom-configured and pre-packaged software components. Gain enhanced features, including Software Bill of Materials (SBOM), CVE scan result reports, and VEX documents. To learn more, visit https://bitnami.com/enterprise
postgresql 10:16:56.58 INFO ==>
postgresql 10:16:56.60 INFO ==> ** Starting PostgreSQL setup **
postgresql 10:16:56.61 INFO ==> Validating settings in POSTGRESQL_* env vars..
postgresql 10:16:56.63 INFO ==> Loading custom pre-init scripts...
postgresql 10:16:56.63 INFO ==> Initializing PostgreSQL database...
postgresql 10:16:56.64 INFO ==> pg_hba.conf file not detected. Generating it...
postgresql 10:16:56.65 INFO ==> Generating local authentication configuration
postgresql 10:16:56.66 INFO ==> Deploying PostgreSQL with persisted data...
postgresql 10:16:56.68 INFO ==> Configuring replication parameters
postgresql 10:16:56.71 INFO ==> Configuring fsync
postgresql 10:16:56.72 INFO ==> Configuring synchronous_replication
postgresql 10:16:56.80 INFO ==> Loading custom scripts...
postgresql 10:16:56.81 INFO ==> Loading user's custom files from /docker-entrypoint-initdb.d ...
postgresql 10:16:56.81 INFO ==> Starting PostgreSQL in background...

[bpblanken]

Looks like the startup is healthy at least!

I think the 137 error code indicates an OOM, so the next thing to try would be to increase the default memory limit from 2Gi. You can do this with a custom values file:

seqr-platform:
  seqr:
     postgresql:
        resources:
          limits:
            memory: "8Gi"

The default is set quite low as postgresql isn't particularly resource intensive compared to other parts of seqr.

[ysayyed11]

I have increased the memory limit to 8G.The issue persist.
Events:
Type Reason Age From Message

---

Normal Scheduled 2m48s default-scheduler Successfully assigned default/seqr-postgresql-0 to kind-control-plane
Normal Pulled 2m48s kubelet Container image "bitnamilegacy/os-shell" already present on machine
Normal Created 2m48s kubelet Created container: seqr-postgresql-init-chmod-data
Normal Started 2m47s kubelet Started container seqr-postgresql-init-chmod-data
Normal Pulled 2m45s kubelet Container image "docker.io/bitnamilegacy/postgresql:12.19.0-debian-12-r9" already present on machine
Normal Created 2m45s kubelet Created container: postgresql
Normal Started 2m45s kubelet Started container postgresql
Warning Unhealthy 8s (x13 over 2m8s) kubelet Startup probe failed: 127.0.0.1:5432 - no response

[root@seqr-prod ~]# kubectl describe pod seqr-postgresql-0 | grep -A5 "Limits"
Limits:
memory: 8Gi
Requests:
memory: 8Gi
Liveness: exec [/bin/sh -c exec pg_isready -U "postgres" -h 127.0.0.1 -p 5432] delay=30s timeout=5s period=10s #success=1 #failure=6
Readiness: exec [/bin/sh -c -e exec pg_isready -U "postgres" -h 127.0.0.1 -p 5432

[bpblanken]

Thanks for the response. Looks like it's likely not a memory issue then.

For further debugging I'd recommend some of the steps listed on this ticket which looks like a similar issue. I have seen problems with the password & secret on initial setup, and it's possible that's what's happening here.

I'd try to verify if the postgres process is starting and subsequently failing or is just failing to start at all.