HelmRelease does not find helm chart inside a directory (oci repository)

[paucampana]

Hi all,

I am having problems with a HelmRelease pointing to a helm chart that is inside a folder. I am using a helm oci repository. The registry that I am using is Harbor.

I am using a HelmRelease with a HelmRepository. My chart is available in: registry.example.com/example-repository/directory1/charts/chart-name

If I configure the HelmRepository url with the repository and the directories, and then I only specify the name of the chart in the HelmRelease, it works:

apiVersion: source.toolkit.fluxcd.io/v1beta2
kind: HelmRepository
metadata:
 name: example-repository
 namespace: default
spec:  
 url: "oci://registry.example.com/example-repository/directory1/charts"
 type: oci 
---
apiVersion: helm.toolkit.fluxcd.io/v2beta1
kind: HelmRelease
metadata:
 name: chart-name
 namespace: default
spec:
 releaseName: chart-name
 targetNamespace: default
 chart:
   spec:
     chart: chart-name
     version: 0.0.1
     sourceRef:
       kind: HelmRepository
       name: example-repository
       namespace: default

But, when I modify the HelmRepository url to only point to the repository, and then I write all the path in the HelmRelease, it is not working:

apiVersion: source.toolkit.fluxcd.io/v1beta2
kind: HelmRepository
metadata:
 name: example-repository
 namespace: default
spec:  
 url: "oci://registry.example.com/example-repository"
 type: oci 
---
apiVersion: helm.toolkit.fluxcd.io/v2beta1
kind: HelmRelease
metadata:
 name: chart-name
 namespace: default
spec:
 releaseName: chart-name
 targetNamespace: default
 chart:
   spec:
     chart: directory1/charts/chart-name
     # chart: "/directory1/charts/chart-name" is not working either
     version: 0.0.1
     sourceRef:
       kind: HelmRepository
       name: example-repository
       namespace: default

I get the error message: HelmChart default/chart-name' is not ready`

It is not something about permissions because I am using admin user.

Any idea what can be happening?
Thanks

[souleb]

Hello,

What does kubectl decribe return? In both HelmRepo and HelmCharts. If your registry is private, you have to pass a secretRef to the HelmRepo.

A good way to test the behavior is to try to push/pull with the helm cli. You should have the same results.

[paucampana]

I thought it was possible. Checking the documentation https://fluxcd.io/docs/components/helm/helmreleases/

type HelmChartTemplateSpec struct {
	// The name or path the Helm chart is available at in the SourceRef.
	// +required
	Chart string `json:"chart"`

so for this lines I understand that it can also work with a path

[makkes]

The docs should probably be a little more specific but here's the crucial part:

The chart.spec.chart can either contain:

• The name of the chart as made available by the HelmRepository (without any aliases), for example: podinfo
• The relative path the chart can be found at in the GitRepository, for example: ./charts/podinfo

https://fluxcd.io/docs/components/helm/helmreleases/#helm-chart-template

[defreng]

I think it would be great if we could also specify the path inside the HelmRelease 🙂

... at least in our case that would help us to avoid creating a lot of different HelmRepository resources

[makkes]

Actions speak louder than words so I created a PR implementing the change: fluxcd/source-controller#856

[defreng]

amazing 😍

[kingdonb]

As mentioned in the thread above, a PR implementing the change landed here: fluxcd/source-controller#856

and it landed in Source controller v0.26 👍 it will be coming in the next Flux release, v0.32.0, due out any day now