Helm installation, suddenly pod cannot be started. could not access the server configuration

[coolize]

Hi, I've been running ParadeDB from the documentation since it was v0.8.5
from the documetation before, the helm installation uses image latest..
Now suddenly the database POD cannot run anymore, returns this in log

`chmod: changing permissions of '/var/run/postgresql': Read-only file system

PostgreSQL Database directory appears to contain a database; Skipping initialization

postgres: could not access the server configuration file "/bitnami/postgresql/data/postgresql.conf": No such file or directory`

[philippemnoel]

Hi @coolize. Apologies for this, and thank you for reporting.

In v0.9.0, we've converted our Dockerfile and Kubernetes Helm Chart from Bitnami over to official Postgres and CloudNativePG, respectively. This is so to offer a more production-ready experience for our customers.

Unfortunately, this was a breaking change. We don't plan to make such a breaking change again, and apologize for the issue. You will need to deploy the new Helm Chart and Dockerfile. Please make sure to be on our Dockerfile version v0.9.1+, as it contains a hotfix to launching the new CloudNativePG cluster, and to be on our Helm chart version v0.6.6+.