Bitnami registry changes

[bushjames]

Request Summary:

See: bitnami/charts#35164 etc...

Bitnami are moving away from maintaining public images/charts for some backing services that we depend on.

We need to both update our current image/chart registry locations to point to the "legacy" registry and seek alternatives to bitnami full stop.

Request Details:

• Deadline: asap
• Impact (Teams): Developers, adopters, testers etc...
• Impact (Components): MySQL, Redis, MongoDB, Kafka etc..

Artifacts:

• HELM charts

Accountability:

• Owner: DA
• Raised By: Kalin Krustev (kalin.krustev@infitx.com)

Decision(s):

1. In the short term, change bitname image paths to new legacy registry
2. Immediately begin replacing bitnami image dependencies with alternatives:

• MySQL, replace with Percona

• Redis, replace with official redis image

• MongoDB, replace with official image

• Kafka, replace with official image

• Approved By: JB, JO, PB, SK, VK.

Follow-up:

• Close issue once all images have been migrated away from bitnami registries.

[igor-soldev]

Hi @bushjames,

If the recent Bitnami image changes are causing trouble, we at SolDevelo maintain fully compatible replacements — including Kafka — that you can drop in.

https://soldevelo.com/services/bitnami-container-images-maintained-by-soldevelo/

[bushjames]

@elnyry-sam-k reports that moves to legacy bitnami repos are in current release candidate, however these will be moved to official images before the release is made.

[bushjames]

v17.2.0 will continue to use "legacy" bitnami repo so as to not delay the release. Migration will happen soon after the release.