Deprecated image in deployment-db manifest can potentially lead to data loss for k8s setup

[david-sykora]

Bug Description

Recently there has been a transition from using twentycrm/twenty-postgres to twentycrm/twenty-postgres-spilo. The mount path has been changed, but the image for k8s db deployment has not been changed. The old image uses the data path /bitnami/postgresql and the new one /home/postgres/pgdata. This leads to postgres data being stored in a directory that is not persistent - as I could have found out the hard way.

Expected behavior

The data should be stored in a directory that is mounted

Possible solution

It should be enough to modify the deployment-db manifest image

[BOHEUS]

@david-sykora that's because k8s files are maintained by the community as it's described here in docs so it's possible that community maintainer didn't have time to adjust them to newest changes, if you know how to fix them, feel free to create a PR

[david-sykora]

Hi @BOHEUS! I opened a pull request that addresses the problems in this issue #9447