keycloak update to 7.2.0-bb.1
Package Merge Request
Package Changes
https://repo1.dso.mil/big-bang/product/packages/keycloak/-/blob/7.2.0-bb.1/CHANGELOG.md
Package MR
big-bang/product/packages/keycloak!351 (merged)
For Issue
Closes big-bang/product/packages/keycloak#301 (closed)
Upgrade Notices
-
BREAKING DATABASE CHANGE: The bundled internal PostgreSQL database has been updated from PG17 to PG18 and moved from the deprecated Bitnami image/layout to the Iron Bank
opensource/postgres/postgresqlimage/layout. Platform One does not support the bundled internal PostgreSQL database for production deployments; this option should only be used for development or CI pipelines. -
DO NOT UPGRADE WITHOUT A DATABASE BACKUP if you need to preserve data from the bundled database. Existing bundled database data is not automatically migrated or reused by the new image layout. To preserve data, export from the old bundled PG17 database with
pg_dump/pg_dumpall, upgrade to this release, then restore into the new PG18 database withpg_restore/psql. -
If you already upgraded without exporting, do not delete the PVC. The old Bitnami-layout PG17 data remains on the PVC, but the new PG18 image uses a different data directory. Roll back to the previous chart/image to access the old data and export it manually.
Regular database backups and best practices should be followed.