helm repo update fails intermittently

[akshaymankar]

What steps will reproduce the bug?

Add the Bitnami Helm repo and try to update it.

What is the expected behavior?

helm repo update succeeds consistently.

What do you see instead?

Getting updates for unmanaged Helm repositories...
...Unable to get an update from the "https://charts.bitnami.com/bitnami" chart repository:
	stream error: stream ID 1; INTERNAL_ERROR; received from peer

[reixd]

Same here. Happens on AWS eu-west-1 but not in eu-central-1

[pkruk]

We have the same issue:

Error: could not find : chart external-dns not found in https://charts.bitnami.com/bitnami: looks like "https://charts.bitnami.com/bitnami" is not a valid chart repository or cannot be reached: stream error: stream ID 1; INTERNAL_ERROR
187
Error: Process completed with exit code 1.

[robertnagy86]

We also have the same issue.

Unknown desc = `helm repo add bitnami https://charts.bitnami.com/bitnami` failed exit status 1: Error: looks like "https://charts.bitnami.com/bitnami" is not a valid chart repository or cannot be reached: stream error: stream ID 1; INTERNAL_ERROR; received from peer

[koendelaat]

+1

[aleshav]

same here, also accessing from aws eu-west-1

[Mykhailov3]

Same for me.

[mmadhur-cops]

+1

[ikramelbrahli]

+1

[BenjaminPiffeteau]

+1

[vinodkumar-wagh]

+1
We are also facing the same issue. Did anyone found any root cause for this.

[WesleyCharlesBlake]

Also facing issues here. Wasnt there recently some SSL/TLS changes to bitnami?? Not sure where I read it. However this is affecting all apps that have a dependancy on bitnami helm repos

[WesleyCharlesBlake]

wait, is it not because of the OCI registry only oci

[carrodher]

Apologies for the inconvenience. We are currently investigating internally to determine if there is any issue with the location where the index.yaml file or Helm charts are hosted. Please rest assured, that no intentional changes have been made recently that would affect this.

That said, please note that this method of consuming Bitnami Helm charts is neither the default nor the recommended approach. We strongly encourage consuming Bitnami Helm charts as OCI artifacts. For more information, please refer to this issue.

[carrodher]

Update: Bitnami Helm charts index.yaml is served via CloudFlare where it seems there are ongoing incidents according to https://www.cloudflarestatus.com/

[mmadhur-cops]

I think this issue can be closed now. @carrodher

[msdolbey]

I think this issue can be closed now. @carrodher

Same here - it's working for us now and we got over the hump.

[alexsorkin]

Seems someone did a "great" job of ruining the http registry index:
message: 'chart pull error: failed to download chart for remote reference: Get "oci://registry-1.docker.io/bitnamicharts/thanos:15.9.2": unsupported protocol scheme "oci"' reason: ChartPullFailed
This is being returned by http registry search.

[carrodher]

Seems someone did a "great" job of ruining the http registry index: message: 'chart pull error: failed to download chart for remote reference: Get "oci://registry-1.docker.io/bitnamicharts/thanos:15.9.2": unsupported protocol scheme "oci"' reason: ChartPullFailed This is being returned by http registry search.

See #30110

[alexsorkin]

HTTP registry MUST point to HTTP urls...
This decision just ruined delivery pipelines in 100.000 companies having PCI envs, and private chart proxies.

$ helm show values redacted-private/thanos Error: failed to fetch https://redacted-private-registry/registry-context/api/helm/redacted-private/oci://registry-1.docker.io/bitnamicharts/thanos:15.9.2 : 404

All Proxied Charts are now broken.

[github-actions]

This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.