-
Notifications
You must be signed in to change notification settings - Fork 45
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: FORMS-1587 set up crunchydb #1536
Conversation
We need to do database upgrades, and part of that is to replace the standalone PostgreSQL pod with a CrunchyDB cluster.
We copy over the Helm charts so that our deployments are consistent and don't change due to changes in the external repo.
b5b1b8d
to
a53d78b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good to me, we may want to configure the schedules at some point to allow for a limit on incremental backups and a time retention for full backups.
Yes indeed! This PR is a copy of the repo for creating a CrunchyDB cluster. The PRs that follow will be the settings specific to our clusters. |
As part of the database upgrades we will be switching from standalong Patroni to CrunchyDB (aka managed Patroni).
This PR is to keep a copy of the Helm charts in our repo. This is good because it means we will have consistent deployments of CrunchyDB with no surprises if the Helm charts in the external repo change. This is bad because we will periodically need to update these files from the upstream repo, but it should be as simple as dropping the new files overtop and committing the changes.
Other PRs will follow to supply the parameters used for each of our database, changes to the CI/CD pipeline, etc.
Description
Type of Change
fix (a bug fix)
Checklist