Utilize Single Postgres DB Installation in Dev/CI
Extract from: https://repo1.dso.mil/platform-one/big-bang/apps/developer-tools/gitlab/-/blob/main/chart/values.yaml#L1032
## could not get IronBank hardened image to work with the bitnami postgres sub-chart
registry: registry.dso.mil
repository: platform-one/big-bang/apps/developer-tools/gitlab/postgresql
tag: 12.7.0
I have a feeling we just gave up on fixing IronBank or adding a compatible version in IronBank, then we keep adding workarounds, and so my own cluster is having 3 lost children from outside IronBank:
gitlab-postgresql-0: registry.dso.mil/platform-one/big-bang/apps/developer-tools/gitlab/postgresql:11.9.0,
keycloak-postgresql-0: registry.dso.mil/platform-one/big-bang/apps/security-tools/keycloak/postgresql:11.8.0-debian-10-r61,
sonarqube-postgresql-0: registry.dso.mil/platform-one/big-bang/apps/developer-tools/sonarqube/postgresql:11.7.0-debian-10-r26,
Can we clean this up?
Instead of each application listed above utilizing their own separate sub-charts, for dev/CI environments let's outline a change to utilize a single bitnami/postgres
or zalando/postgres-operator
(BigBang-ified) installation that any application can utilize.
Will need to confirm, but appears from testing/use that all existing applications that can utilize an "external" DB support both versions 12.X & 13.X (in use in our dogfood release cluster).