Helm charts view doesn't show charts hosted on Sonatype Nexus

Lens Support & Troubleshooting
#1

Recently I tried to install some helm charts hosted on Sonatype Nexus (3.72.0-04) repository. I added repository via helm repo add ... command. New repo appeared at Lens desktop settings as normal. But the problem is that “Helm charts” view doesn’t show any charts from new repo.
The same flow works fine with JFrog artifactory repository. All charts are displayed.

I analyzed differences between thoose Helm repositories and found out only different index.yaml file structures. I.e. nexus index contains only few metadata for every chart:

foo-chart:
  - name: foo-chart
    description: foo-chart
    version: 1.0.0
    created: 2024-01-01T00:00:00.000Z
    digest: 437c3501b2ae169e2d8276e4e254fff013e338e8682c9e037b1e30a8787c33ee
    urls:
    - foo-chart-1.0.0.tgz

In the same time JFrog repository has:

foo-chart:
  - apiVersion: v2
    created: 2024-11-01T10:50:48.683781158Z
    description: foo-chart
    digest: 437c3501b2ae169e2d8276e4e254fff013e338e8682c9e037b1e30a8787c33ee
    name: foo-chart
    urls:
    - https://foo.com/artifactory/bar/foo-chart-1.0.0.tgz
    kubeVersion: '>= 1.23.0'
    dependencies: ...
    annotations: ...
    version: "1.0.0"

Is that a bug in Lens or there are some restrictions on Helm repository vendors that are supported?

#2

Hello @alian_object , Thank you for reaching out ! I have contacted our development team regarding your issue .

#3

It seems that Lens doesn’t allow it because the apiVersion field is missing. Looking at Helm | Charts this seems to be a required field. I think it’s a bug with Sonatype Nexus, someone else noticed the same in apiVersion missing for every entry in the helm index.yaml - Sonatype Nexus Repository - Sonatype Community.

1 Like
#4

I agree it’s an old issue of Nexus. But I’m afraid no one is going to fix it on their side.

On other hand, I believe Lens could introduce support for such repo. Helm itself supports such index file despite of missing some required fields. And I think Lens could support it too.

What do you think?

#5

I’ve addressed this with the relevant team, and we’ll evaluate whether we can make the necessary adjustments on our side. Our goal is to make your work easier, so thank you for bringing this up!

1 Like
#6

Hello! Any news on that?

#7

We’ve added it to our backlog, but don’t have a timeline for implementation yet. We’ll keep this thread updated if there’s any progress.