Helm Chart - postgresql container in crashbackoff loop

Steps to reproduce the problem

Pulled latest from git Modified values.yaml to include relevant info Deployed via helm

Expected behaviour

postgresql pod runs as excepted

Actual behaviour

Postgresql pod is in crashbackoff loop

Detailed description

Warning FailedScheduling 2m27s default-scheduler 0/3 nodes are available: 3 pod has unbound immediate PersistentVolumeClaims. preemption: 0/3 nodes are available: 3 Preemption is not helpful for scheduling. Normal Scheduled 2m26s default-scheduler Successfully assigned mastodon/mastodon-postgresql-0 to k8s3 Normal Pulled 81s (x4 over 2m18s) kubelet Container image "docker.io/bitnami/postgresql:14.2.0-debian-10-r14" already present on machine Normal Created 71s (x4 over 2m18s) kubelet Created container postgresql Normal Started 68s (x4 over 2m18s) kubelet Started container postgresql Warning BackOff 54s (x13 over 2m15s) kubelet Back-off restarting failed container

The PVC does get created and bound without a problem.

There are no errors, and this is all I see in the pod logs:

postgresql 16:23:14.56

postgresql 16:23:14.56 Welcome to the Bitnami postgresql container postgresql 16:23:14.56 Subscribe to project updates by watching https://github.com/bitnami/bitnami-docker-postgresql postgresql 16:23:14.57 Submit issues and feature requests at https://github.com/bitnami/bitnami-docker-postgresql/issues postgresql 16:23:14.57 postgresql 16:23:14.64 INFO ==> Starting PostgreSQL setup postgresql 16:23:14.69 INFO ==> Validating settings in POSTGRESQL_* env vars.. postgresql 16:23:14.71 INFO ==> Loading custom pre-init scripts... postgresql 16:23:14.75 INFO ==> Initializing PostgreSQL database... postgresql 16:23:14.80 INFO ==> pg_hba.conf file not detected. Generating it... postgresql 16:23:14.81 INFO ==> Generating local authentication configuration

Specifications

Mastodon: latest

mastodon / chart