upgrade fro 8.5.1 to 8.6.0: Error: invalid_reference: invalid tag

[mpechner-akasa]

Name and Version

bitnami/external-dns/8.6.0

What architecture are you using?

amd64

What steps will reproduce the bug?

upgrade from 8.5.1 to either 8.6.0 or 8.6.1
Get this error: "Error: invalid_reference: invalid tag"

Are you using any custom parameters or values?

resource "helm_release" "external_dns" {
  namespace        = local.external_dns_ns
  create_namespace = true

  name       = "external-dns"
  repository = "https://charts.bitnami.com/bitnami"
  chart      = "external-dns"
  version    = var.external_dns_version

  values = [
    templatefile("${path.module}/config/external-dns-values.yaml.tftpl", {
      external_dns_role_arn = module.external_dns_irsa_role.iam_role_arn,
      aws_region            = var.aws_region
    })
  ]
}

crd:
  create: true
sources:
  - crd
  - service
  - ingress
  - traefik-proxy
txtPrefix: MYCOMPANY
aws:
  region: ${aws_region}
metrics:
  enabled: true
  serviceMonitor:
    enabled: true
serviceAccount:
  annotations:
    "eks.amazonaws.com/role-arn": ${external_dns_role_arn}

What is the expected behavior?

The update from 8.5.1 to 8.6.0 or 8.6.1 would work.

What do you see instead?

 Error: invalid_reference: invalid tag
│ 
│   with module.eks_defaults.module.ingress_controller.helm_release.external_dns,
│   on ../../modules/eks_default_installations/ingress-controller/external-dns.tf line 6, in resource "helm_release" "external_dns":
│    6: resource "helm_release" "external_dns" {

[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.

[mpechner-akasa]

Thank you that was it.

resource "helm_release" "external_dns" {
  namespace        = local.external_dns_ns
  create_namespace = true

  name       = "external-dns"
  repository = "oci://registry-1.docker.io/bitnamicharts"
  chart      = "external-dns"
  version    = "8.6.1"

  values = [
    templatefile("${path.module}/config/external-dns-values.yaml.tftpl", {
      external_dns_role_arn = module.external_dns_irsa_role.iam_role_arn,
      aws_region            = var.aws_region
    })
  ]
}