Bitnami Image/Helm Chart Deprecation Plan #3148
Adam-D-Lewis
started this conversation in
General
Replies: 1 comment
-
I vote to remove Minio as soon as possible, rather than replacing it with Docker. For Redis, I'm not familiar with Vakkey. Still, I would be hesitant to replace it since it's a widely adopted standard, making it easier to find documentation on the web for integrating services and components within it. For PostgreSQL if we keep it, we need to attest:
If we replace it with another image, that also might be fine. I don't have any points against it, besides the possibility that this is a security flag from airgapped deployments.... those images need to be listed as accepted resources/tools |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
With the deprecation of Bitnami images, the short term migration plan is to use bitnami legacy containers. I've opened this issue to discuss longer term plans around the issue.
The Bitnami images running on a current GCP deployment from
main
are listed below:So really, just 3 services in nebari core (plugins like https://github.com/nebari-dev/nebari-mlflow-plugin can also be affected, but are not handled here)
Postgres
Looks like alternatives exist e.g. https://opensource.zalando.com/ and https://github.com/cloudnative-pg/cloudnative-pg both have permissive licenses
Minio
We've been stuck on a 2021 version since before the license change, but should look at alternatives for this.
Redis
Perhaps we should switch to valkey. Looks like they are creating their own official helm chart - valkey-io/valkey#2371, https://github.com/valkey-io/valkey-helm
Beta Was this translation helpful? Give feedback.
All reactions