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: FORMS-1587 set up crunchydb #1536

Merged
merged 8 commits into from
Dec 16, 2024
Merged

Conversation

WalterMoar
Copy link
Collaborator

@WalterMoar WalterMoar commented Dec 4, 2024

Note: this PR contains the README.md at the top, and everything else is copied from https://github.com/bcgov/crunchy-postgres

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

  • I have read the CONTRIBUTING doc
  • I have checked that unit tests pass locally with my changes
  • I have run the npm script lint on the frontend and backend
  • I have added tests that prove my fix is effective or that my feature works
  • I have added necessary documentation (if appropriate)
  • I have approval from the product owner for the contribution in this pull request

@WalterMoar WalterMoar changed the title fix: set up crunchydb for fider fix: FORMS-1587 set up crunchydb for fider Dec 4, 2024
@WalterMoar WalterMoar changed the title fix: FORMS-1587 set up crunchydb for fider fix: FORMS-1587 set up crunchydb Dec 13, 2024
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.
Copy link
Collaborator

@jasonchung1871 jasonchung1871 left a 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.

@WalterMoar
Copy link
Collaborator Author

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.

@WalterMoar WalterMoar merged commit e677876 into bcgov:main Dec 16, 2024
5 checks passed
@WalterMoar WalterMoar deleted the fix/1587-crunchydb branch December 16, 2024 16:29
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.

2 participants