Quickstart Guide References Bitnami Charts, is this affected by "Upcoming changes to the Bitnami catalog (effective August 28th, 2025)"

[nelsonjchen]

https://helm.sh/docs/intro/quickstart/

bitnami/charts#35164

Admittedly, I'm still a bit green to some of this, but I'm unclear if this will affect things. Looking at the bitnami/mysql chart, I think it references a non-:latest tag. Is that going to break come August 28th?

[github-actions]

This issue has been marked as stale because it has been open for 90 days with no activity. This thread will be automatically closed in 30 days if no further activity occurs.

[benoittgt]

I think it still need to be look at.

[TerryHowe]

Anyone willing to work on this? I'm not a bitnami user ATM, so I don't know all the impacts.

[Iam-Karan-Suresh]

Hi @TerryHowe ! I’d like to take a look at this issue and work on it, if that’s okay.

From my understanding, the main concern is that the Helm Quickstart
currently depends on Bitnami charts, which may become confusing or fragile
due to upcoming Bitnami catalog and image changes (e.g. legacy image overrides).

My proposed approach would be:

• Avoid using Bitnami charts in the main Quickstart flow
• Update the example to use a vendor-neutral, OCI-based chart (for example via GHCR)
• Add a short note acknowledging Bitnami and other third-party providers, so existing users aren’t confused

This keeps the Quickstart stable and beginner-friendly while still pointing users
to third-party options intentionally.

If this approach sounds reasonable, I’m happy to open a PR.
Please let me know and feel free to assign the issue to me.
Thanks!

[lambdasierra]

I can confirm that the current quick-start instructions did not work for me.

Adding the repository works:

helm-www/docs/intro/quickstart.md

Line 41 in 17ce85a

$ helm repo add bitnami https://charts.bitnami.com/bitnami

The repository update works:

helm-www/docs/intro/quickstart.md

Line 63 in 17ce85a

$ helm repo update # Make sure we get the latest list of charts

The installation appears to work:

helm-www/docs/intro/quickstart.md

Line 64 in 17ce85a

$ helm install bitnami/mysql --generate-name

$ helm install bitnami/mysql --generate-name
NAME: mysql-1767987296

although it prints the following warning:

⚠ WARNING: Since August 28th, 2025, only a limited subset of images/charts are available for free.
    Subscribe to Bitnami Secure Images to receive continued support and security updates.
    More info at https://bitnami.com and https://github.com/bitnami/containers/issues/83267

However, the pod is stuck in a loop trying to download the image:

$ kubectl describe pod/mysql-1767987296-0
...
Events:
  Type     Reason            Age                    From               Message
  ----     ------            ----                   ----               -------
  Warning  FailedScheduling  2m52s (x4 over 2m52s)  default-scheduler  0/1 nodes are available: pod has unbound immediate PersistentVolumeClaims. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling.
  Normal   Scheduled         2m52s                  default-scheduler  Successfully assigned default/mysql-1767987296-0 to minikube
  Normal   Pulling           84s (x4 over 2m52s)    kubelet            Pulling image "docker.io/bitnami/mysql:9.4.0-debian-12-r1"
  Warning  Failed            83s (x4 over 2m51s)    kubelet            Failed to pull image "docker.io/bitnami/mysql:9.4.0-debian-12-r1": Error response from daemon: manifest for bitnami/mysql:9.4.0-debian-12-r1 not found: manifest unknown: manifest unknown
  Warning  Failed            83s (x4 over 2m51s)    kubelet            Error: ErrImagePull
  Normal   BackOff           4s (x10 over 2m51s)    kubelet            Back-off pulling image "docker.io/bitnami/mysql:9.4.0-debian-12-r1"
  Warning  Failed            4s (x10 over 2m51s)    kubelet            Error: ImagePullBackOff

[TerryHowe]

A pull request would be great from someone. As well as having a working example, I think we should encourage people to use OCI registries over helm repositories. The problem is I'm not sure what to put in this guide to replace this. The easiest thing may be a helm create, package and install combo. I'd be curious what other people think would be good to replace this.

[Iam-Karan-Suresh]

Hi @TerryHowe and maintainers! I’ve opened a pull request addressing this issue.

The Quickstart example has been updated to use a vendor-neutral
helm create → helm install workflow, with a short note acknowledging
third-party repositories and OCI-based charts.

Please let me know if you have any feedback or would like any adjustments
or changes made. Happy to iterate—thanks for reviewing!
#1982