fix(helm): Correct Postgres volume mount path for persistence #9395
+1
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR fixes an issue where PySyft datasets and other Postgres data were lost upon cluster reboot or pod restart.
The root cause was that the Postgres StatefulSet in the Helm chart was mounting the persistent volume to
tmp/data/db, but the Postgres container writes to/var/lib/postgresql/databy default. This meant data was being written to the container's ephemeral storage instead of the Persistent Volume.This change updates the
mountPathin postgres-statefuleset.yaml to/var/lib/postgresql/data, ensuring data persistence.Using
Affected Dependencies
None.
How has this been tested?
mountPathis correctly set to/var/lib/postgresql/data.Checklist