Azure-devops-docs: How to Deploy from ACR Helm Chart Repositories

Created on 2 Nov 2018 · 4Comments · Source: MicrosoftDocs/azure-devops-docs

ACR Helm Chart Repositories are a new preview part of Azure Container Registry. Currently, there is no documentation on how to deploy from ACR Helm Chart Repositories.

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: fc7eeb7f-4e6b-8fee-1d7f-582cfb018b02
Version Independent ID: 00fb3082-1069-9060-012c-0b6d75ef120b
Content: Package and Deploy Helm Charts task - Azure Pipelines & TFS
Content Source: docs/pipelines/tasks/deploy/helm-deploy.md
Product: devops
GitHub Login: @erickson-doug
Microsoft Alias: dastahel

Source

RehanSaeed

Most helpful comment

Removing --force did the trick. I think I must have done that, when I was messing about trying to work out what version of helm was running.

Also, your link was a great guide.

RehanSaeed on 7 Nov 2018

👍3

All 4 comments

I want to deploy as part of a 'Release' and not 'Build'. I used the Deploy Helm Chart template and tried to fill in the fields but got stuck on the 'Chart Path' field. I don't have a path to a chart, I have a Helm repository.

RehanSaeed on 2 Nov 2018

I created a build to publish Helm charts using Azure Pipelines but I found two major stumbling blocks to doing so. @steved0x @azooinmyluggage @shashankbarsin is there someone I can feedback to?

I had to run helm init on the Azure pipelines agent or I could not run helm package --dependency-update. More info in https://github.com/helm/helm/issues/4870.
For reasons I don't understand az acr helm push simply does not work unless I run helm version first. I don't really know why, seems really flaky. When I do not do so, I get the following error:

Executing: /usr/bin/az acr helm push --force --name '' --username '' --password '*' "/home/vsts/work/1/s/Artefacts/Ummati-1.0.165-master.tgz"
ERROR: Error: You have requested chart that does not exist. Correlation ID: a57301c1-9fdc-47c5-ba03-0a5028aa9ffb.

RehanSaeed on 3 Nov 2018

JFYI @RehanSaeed: here is how I have used this feature through my CI/CD pipeline with Azure DevOps: https://alwaysupalwayson.blogspot.com/2018/10/helm-charts-repository-with-azure.html

Regarding helm init, yes it's mandatory to do so with the --client-only parameter during your Build/CI pipeline.

Regarding your error "You have requested chart that does not exist.", if you remove the --force parameter you won't get this error. Just tried with and was able to reproduce your error; without it, no error. It's by the way a known issue: https://github.com/Azure/acr/issues/142. Really weird about the helm version "workaround" you found...