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

Unable to deploy the helm3 charts from azure container registery #655

Closed
basavarajb opened this issue Jan 12, 2021 · 7 comments
Closed

Unable to deploy the helm3 charts from azure container registery #655

basavarajb opened this issue Jan 12, 2021 · 7 comments

Comments

@basavarajb
Copy link

Guide me to deploy the charts from azure acr.
in the screen shot i've attached the error

image

@jrhouston
Copy link
Contributor

Hi @basavarajb it looks like Azure's container registry supports Helm charts via OCI, which is currently an experimental feature of Helm. You could try enabling it by setting export HELM_EXPERIMENTAL_OCI=1 in your environment.

@basavarajb
Copy link
Author

yes i executed command on windows 10 set HELM_EXPERIMENTAL_OCI=1

is my below code correct while getting the chart form acr

resource "helm_release" "example" {
  name       = "shopingcart"
   chart      = "https://xxxxxxx.azurecr.io/helm/shopingcart:v1"
  values     = [local.helm_chart_values]
}

@jemag
Copy link

jemag commented Jan 26, 2021

Having the same issue on Linux with HELM_EXPERIMENTAL_OCI=1.

However, it is really hard to get actual feedback on what is happening when trying to download the chart. Even if I were to enter a totally wrong repository like :

resource "helm_release" "buildkit" {
  name 		 = "buildkit"
  repository = "zing.buzz.io"
  chart      = "buildkit-chart"
}

The feedback will still remain :
image

No additional details seems to be provided, even with TF_LOG=TRACE.

If I were to do the same with Helm, I would get some basic feedback that could orient me in the right direction:
image

So it may be that OCI is not supported at all with helm_release, or we are entering URLs that do not fit what is expected and fails continuously what that same error message.

Either way, I am guessing this is a problem for both ACR and ECR users. Would love to know if anyone found a workaround

@sziegler-skyhook
Copy link

I'm also running into this issue in Azure ACR, can anyone confirm if the Terraform Helm provider supports installing Helm charts from an OCI repository?

@val3r10
Copy link

val3r10 commented Jun 25, 2021

It is not clear at all if the ACR is supported or what the format of the url should look like:
image

resource "helm_release" "nginx-acr-private" {
name = "ingress-nginx"
chart = "ingress-nginx"
repository = "https://xxxxxxxxxxxxx.azurecr.io/helm/nginx:v1"
repository_username = var.acr_admin_username
repository_password = var.acr_admin_password
}

@github-actions
Copy link

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!

@github-actions
Copy link

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 29, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants