Bitnami/Broadcom mitigation

[bstrdsmkr]

Describe the bug

Our chart depends on bitnami/postgres-ha chart to provide Postgres. Broadcom bought Bitnami and subsequently has started moving their catalog behind a paywall. After 28 Aug 2025, the current repo will be unavailable. All images and charts will have been relocated. Unfortunately, there is currently no community consensus on a replacement.

Impact:

• New Kubernetes installations will fail as the dependencies will be unreachable
• Existing Kubernetes installations will begin failing as their image caches age out and containers restart

Work Required:

• Select a replacement Postgres provider
• Update chart dependencies to new provider
• Integrate new provider (credential provisioning, service location communication, etc)

[sashakames]

We are close to having another release but clearly this would be a crucial fix to include in the next release tag if we can identify the replacement image name to use.

[sashakames]

@jasonb5 and @downiec discussed a change to the postgres settings to enable a broader use, decouple the database for helm deployments. Is it clear what change needs to be made?

[jasonb5]

@sashakames I have a PR coming to replace bitnami with a simple single node postgres database with the option/preferred method of using an external postgres database via CNPG, StackGres, Zalando, etc.

[sashakames]

#854