Invalid Tag message for multiple helm charts

[nicl-dev]

Name and Version

bitnami/external-dns-8.7.0, bitnami/keycloak-24.3.0, bitnami/thanos-15.9.2

What architecture are you using?

amd64

What steps will reproduce the bug?

After trying to upgrade our helm-charts we cannot pull newer chart versions. For example external-dns:

helm repo update
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "bitnami" chart repository
Update Complete. ⎈Happy Helming!⎈

helm pull --untar --repo https://charts.bitnami.com/bitnami external-dns --version 8.7.0
Error: invalid_reference: invalid tag

The same thing happens with the keycloak and thanos charts. The versions are all taken from artifacthub.io.

For external-dns the latest available version from your repository is 8.5.0.
For keycloak it is 24.2.0.
For thanos it is 15.8.1.

Seems like I can't access anything that's younger than early November. This happens both on my local machine and on our AWS clusters.

What is the expected behavior?

Helm pulling the new chart version.

What do you see instead?

Error: invalid_reference: invalid tag

[nicl-dev]

And right after typing this it works, weird. Sorry for the confusion.

Still doesn't work.

[Jasper-Ben]

Nah, it's not just you. We have the same issue, e.g. upgrading from redis chart 20.3.0 to anything newer.

[Jasper-Ben]

Between redis 20.3.0 (the last version we could successfully upgrade to) and redis 20.4.0 there have been changes to github workflows that seem to be relevant for tagging. My uneducated guess is that there is a bug somewhere there. In the redis chart there haven't been any relevant changes that could cause this issue.

[carrodher]

As reported in helm/helm#13466, this problem stems from how the helm ... --repo ... command handles an index.yaml file containing OCI URLs.

Why is this issue appearing now?

Historically, Bitnami Helm charts were accessed by adding the Bitnami repository to the Helm CLI:

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

or by directly installing/pulling a specific Helm chart using the --repo flag:

$ helm pull --repo https://charts.bitnami.com/bitnami foo

In April 2023, Bitnami introduced support for the OCI format, recommending OCI-based installation as the primary method going forward. For example:

helm pull oci://registry-1.docker.io/bitnamicharts/external-dns --version 8.6.0

As detailed in our recent announcement and #30110, the traditional method is now being deprecated. Consequently, the index.yaml served at https://charts.bitnami.com/bitnami now uses OCI URLs, exposing the above mentioned issue in the Helm CLI's handling of these URLs.

[nicl-dev]

Well, another case of RTFM. I was looking for the cause in your most recent announcement about Bitnami Premium because I had a feeling something like this might have happened, but unfortunately, I didn’t scroll far enough. Thank you for pointing me in the right direction.