Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: postgres data mountpoint #3556

Merged
merged 2 commits into from
Nov 4, 2022
Merged

fix: postgres data mountpoint #3556

merged 2 commits into from
Nov 4, 2022

Conversation

mxyng
Copy link
Collaborator

@mxyng mxyng commented Nov 4, 2022

Summary

Using the data mountpoint directly causes problems for postgres in certain scenario where the directly may not initialize empty. Instead, use a subdirectory under the mountpoint to store the actual data.

  • Add migration to move data previously stored in the mountpoint to the subdirectory (/var/lib/postgresql/data -> /var/lib/postgresql/data/pgdata)
  • Fix postgres health checks to use the right user and database name
  • Bump appVersion to 0.16.1, chart version to 0.20.5

Testing Migration

  • Install Infra locally with chart 0.20.4
  • Load some data (users, groups)
  • Upgrade chart
  • Verify data still exists

Testing AWS

  • Install Infra with chart 0.20.4.
  • Postgres pod goes into crash loop
  • Install updated chart
  • No crash loop

Related Issues

Resolves #3124
Resolves #3555

@mxyng mxyng merged commit ab4bbc8 into main Nov 4, 2022
@mxyng mxyng deleted the mxyng/fix-postgres-mountpoint branch November 4, 2022 01:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Crashloopbackoff when deploying postgres container on GKE
2 participants