Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[bitnami/external-dns] unsupported protocol scheme "oci" #31029

Closed
oliveirajoaop opened this issue Dec 13, 2024 · 2 comments
Closed

[bitnami/external-dns] unsupported protocol scheme "oci" #31029

oliveirajoaop opened this issue Dec 13, 2024 · 2 comments
Assignees
Labels
external-dns solved tech-issues The user has a technical issue about an application triage Triage is needed

Comments

@oliveirajoaop
Copy link

Name and Version

bitnami/external-dns

What architecture are you using?

amd64

What steps will reproduce the bug?

1 - Successfully deployed bitnami/external-dns version 8.5.1 to eks version 1.30.6 with flux 2.4.0
2 - Update external dns from version 8.5.1 to 8.6.0, 8.6.1 or 8.7.0

Are you using any custom parameters or values?

No

What is the expected behavior?

The update should run with no errors.

What do you see instead?

Updating the helm-release to version 8.6.0, 8.6.1 or 8.7.0 will result in error with the message:
chart pull error: failed to download chart for remote reference: Get "oci://registry-1.docker.io/bitnamicharts/external-dns:8.6.0": unsupported protocol scheme "oci" and chart pull error.

Additional information

Helm Repo

apiVersion: source.toolkit.fluxcd.io/v1beta2
kind: HelmRepository
metadata:
  name: bitnami
  namespace: flux-system
spec:
  interval: 10m
  url: https://charts.bitnami.com/bitnami

Helm release

---
apiVersion: helm.toolkit.fluxcd.io/v2
kind: HelmRelease
metadata:
  name: external-dns
  namespace: external-dns
spec:
  releaseName: external-dns
  chart:
    spec:
      chart: external-dns
      sourceRef:
        kind: HelmRepository
        name: bitnami
        namespace: flux-system
      version: 8.6.0 (8.6.1 or 8.7.0)
  interval: 1m
@oliveirajoaop oliveirajoaop added the tech-issues The user has a technical issue about an application label Dec 13, 2024
@github-actions github-actions bot added the triage Triage is needed label Dec 13, 2024
@oliveirajoaop
Copy link
Author

Managed to solve the issue the right way with the OCI Repo

@carrodher
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
external-dns solved tech-issues The user has a technical issue about an application triage Triage is needed
Projects
None yet
Development

No branches or pull requests

2 participants