Helm 3

Hi, are you guys planning to support Helm 3 ? It would be nice to deploy chart to k8s without Tiller.

1 Like

Hi Daniel,

The Upgrade a Helm Chart step will work just fine with Helm 3. Of course, please don’t hesitate to reach out if you do have any issues.

If you don’t mind me asking, what made you believe it wouldn’t work with Helm 3?

Maybe i’am doing something wrong but its not working. Iam getting error unknown flag: --skip-refresh. It’s not working with Helm feed as Azure Container Registry and Github either.

Task ID: ServerTasks-1089
Related IDs: Deployments-124, Channels-61, Releases-103, Projects-61, Spaces-1, Environments-21
Task status: Failed
Task queued: niedziela, 01 grudnia 2019 8:02:43 AM +01:00
Task started: niedziela, 01 grudnia 2019 8:02:44 AM +01:00
Task completed: niedziela, 01 grudnia 2019 8:02:47 AM +01:00
Task duration: 3 seconds
Server version: 2019.10.1+Branch.tags-2019.10.1.Sha.bdb544fa5f64dbd44c76f17f939e12da022dda70
Server node: DESKTOP-J45OU76

                | == Failed: Deploy itdepends-app release 0.0.3 to Test ==

08:02:45 Verbose | Guided failure is not enabled for this task
08:02:47 Fatal | The deployment failed because one or more steps failed. Please see the deployment log for details.
| == Failed: Acquire packages ==
08:02:45 Info | Acquiring packages
08:02:45 Info | Making a list of packages to acquire
08:02:45 Verbose | No packages are required on any deployment targets
08:02:45 Fatal | The step failed: Activity failed with error ‘Helm failed to download the chart (Exit code 1). Error output:
| Error: unknown flag: --skip-refresh’.
08:02:45 Verbose | Acquire Packages completed
| Failed: Octopus Server
08:02:45 Error | Helm failed to download the chart (Exit code 1). Error output:
| Error: unknown flag: --skip-refresh
| Failed: Download package itdepends v1.0.0 from Helm repository at https://xxx.azurecr.io/helm/v1/repo/
08:02:45 Verbose | Checking package cache for package itdepends v1.0.0
08:02:45 Info | Downloading itdepends v1.0.0 to package cache…
08:02:45 Verbose | Downloading itdepends v1.0.0 from Helm repository at https://xxx.azurecr.io/helm/v1/repo/ using cache policy UseCache…
08:02:45 Verbose | Downloading package (attempt 1 of 1)
08:02:45 Verbose | version.BuildInfo{Version:“v3.0.0”, GitCommit:“e29ce2a54e96cd02ccfce88bee4f58bb6e2a28b6”, GitTreeState:“clean”, GoVersion:“go1.13.4”}
08:02:45 Error | Error: unknown flag: --skip-refresh
| == Skipped: Step 1: helm ==
08:02:45 Info | Step “helm” runs only when all previous steps succeeded; skipping

Hi @itdependspl,

Thanks for following up and letting us know the outcome of your attempts at getting this to work. I’m sorry to say we were initially incorrect in the assumption that this would just work with Helm 3. However we should certainly support it, so I’ve raised the following issue for you to track.

Please don’t hestitate to get in touch if you have any questions or concerns moving forward. :slight_smile:

Best regards,



I tried to get some answers about the timing of a fix for this on github
[https://github.com/OctopusDeploy/Issues/issues/6048](Issue 6048)
but nobody seem to be monitoring the issue there

Currently Octopus is the only thing in our tool chain that are blocking us from migrating to Helm 3. We are on Octopus v2019.9.10 LTS.

Can you please provide some feedback on the timing of a fix for this. We have migrated what we can to helm 3, but are blocked by Octopus. There are many good reasons for migrating to helm 3 so we really would like to do so asap. Will there be a hotfix for the current LTS or a fix in the next LTS?

All the best,

Hi Jan,

We are working on making the Helm feed and step support Helm v3 right now.
We are likely to ship this in the first week of January, and we can certainly apply a patch to the 2019.9 LTS.

We do apologize for the inconvenience.

Thanks. That was just what I wanted to hear :slight_smile:. A patch for 2019.9. LTS would be great.
Great support as always.


Has this been fixed in the latest LTS? I don’t see anything about it in the release notes and the github issue is still open.

1 Like

@Michael_Richardson. Any news on this issue? We are still waiting for a fix or information that the fix is part of the latest LTS

I’m sorry Jan, the change for this is still coming.
The work was interrupted by the Christmas break, but we are working on it at this moment as a priority. The engineering team believe it should be complete by the end of the week.

We sincerely apologize for the delay. We know this one has taken too long.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.