As SIMS technical team, we need to ensure that our tools and platform are maintained at current versions. Postgres 12 is EOL as of November 2024 and must be upgraded prior to that. As part of this migration, ideally the team would use technologies that treat the DB more as a service.
Acceptance Criteria
[ ] Deploy new DB and PgBouncer to all environments
[ ] Dev
[ ] Test
[ ] Staging
[ ] Production
[ ] Update application connection to use PgBouncer
[ ] Document, verify, and execute process to migrate Production data
[ ] Document, test and execute the removal of the old database
[ ] Use Helm for Deployment
Technical Context
Decisions:
Use Crunchy Operator and Helm to create the DB
Review Items:
Ideally use PG 16 for longevity but currently installed operator doesn't support this.
Current DB name is SIMSDB but Crunchy doesn't like that.
Do we need to expose the postgres super user account?
Sample yaml using Crunchy Operator to deploy Patroni HA Postgres 15 with pgbouncer and pgbackrest.
As SIMS technical team, we need to ensure that our tools and platform are maintained at current versions. Postgres 12 is EOL as of November 2024 and must be upgraded prior to that. As part of this migration, ideally the team would use technologies that treat the DB more as a service.
Acceptance Criteria
Technical Context
Decisions: Use Crunchy Operator and Helm to create the DB
Review Items:
Sample yaml using Crunchy Operator to deploy Patroni HA Postgres 15 with pgbouncer and pgbackrest.
Perform a Point in time recovery