Deploy of a Helm chart from AZURE CONTAINER REGISTRY in OCI format is not working

[anithapriyanatarajan]

Terraform version, Kubernetes provider version and Kubernetes version

Terraform version: 0.12.3
Helm Provider version:  3.6.1
Kubernetes version: AKS - 1.19.11

Terraform configuration

provider "azurerm" {
  version = "~>2.0"
  features {}
}

data "azurerm_kubernetes_cluster" "credentials" {
  name                = "k8stest"
  resource_group_name = "azure-k8stest"
}

provider "helm" {
  kubernetes {
    host                   = data.azurerm_kubernetes_cluster.credentials.kube_config.0.host
    client_certificate     = base64decode(data.azurerm_kubernetes_cluster.credentials.kube_config.0.client_certificate)
    client_key             = base64decode(data.azurerm_kubernetes_cluster.credentials.kube_config.0.client_key)
    cluster_ca_certificate = base64decode(data.azurerm_kubernetes_cluster.credentials.kube_config.0.cluster_ca_certificate)

  }
}

resource "helm_release" "ariflow-tf" {
  name       = "airflow"
  repository  = "https://anfmpacr.azurecr.io/helm/v1/repo"
  repository_username = "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
  repository_password = "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
  chart      = "airflow"
  version    = "10.1.1"
  namespace  = "airflow-dev"
  create_namespace  = "true"

  

# values = [
 #   "${file("values.yaml")}"
 # ]

 set {
   name  = "cluster.enabled"
   value = "true"
 }

  set {
    name  = "metrics.enabled"
    value = "true"
 }

 set {
    name  = "service.annotations.prometheus\\.io/port"
    value = "9127"
    type  = "string"
 }

}

Question

The repo URL corresponds to azure container registry URL.
There is a valid helm chart pushed and working fine when pulled using CLI from registry. Attached the screenshot of container registry for proof.
But when using terraform i am always getting error as "Chart not found in Repository". Please help to understand what is missing in the Terraform syntax?

[do0ominik]

Any news on this topic? I am facing the same problem ..

[github-actions]

Marking this issue as stale due to inactivity. If this issue receives no comments in the next 30 days it will automatically be closed. If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. This helps our maintainers find and focus on the active issues. Maintainers may also remove the stale label at their discretion. Thank you!