When using a Helm feed in Octopus, it seems that packages are not found were package versions start with “v”.
For example, Cert Manager from JetStack is versioned with a leading “v” (i.e. v1.0.0), and Octopus does not find any versions of that package. I’ve attached a HAR file containing the request to the feeds API below, just in case it’s helpful.
In an attempt to fix, I fudged the version within the chart.yaml file and added a package to a custom Helm repository (using GitHub pages). This allowed the Helm feed within Octopus to find the package/version, but when deployed to a Kubernetes cluster the chart failed to pull the required Docker containers - I guess the version of these are tied to the version of the Helm chart.
When pulling this package using the helm CLI it can be referenced as version 1.0.0 (no leading v) -
helm pull JetStack/cert-manager --version 1.0.0
Is there a way around this, as I’m kind of stuck without being able to pull the Helm chart that I need.
It looks like we’re all aligned on why it’s not working, so it would be great if a fix did come in a (near) future version of Octopus. Although I kind of think it should be JetStack that fix things on there end really, and I’ve added a comment to an already open issue.
I’ll keep using the script I’ve written for now as it works.