Failed to get helm release YAMLException: duplicated mapping key

[djcristi]

Lens: 2023.12.80831-latest , happens on old versions also

this error . happens on some deployments that have dupplicate mapping keys in the yaml, so when you go to Helm -> Releases it will not show the details of the release, even if the yaml is working.

for example in my case it has 2 containers in the same deployment, so 2 resources definition. Failed to load release: Failed to get helm release resources: YAMLException: duplicated mapping key (16:5) 13 | release: "grimoire" 14 | app.kubernetes.io/version: "1.0.0" 15 | app.kubernetes.io/managed-by: Helm 16 | app: grimoire ----------^ 17 | chart: java-app-1.0.0 18 | release: "grimoire"

[vladelleus]

I have the same issue:

[twoTimesAgnew]

Same issue here as well.

[stevefan1999-personal]

This happens after I changed from VXLAN to GENEVE, updating on my existing Cilium Helm release.

[jseletz-rave]

I'm seeing this issue as well

[zackery-parkhurst]

I too have this issue.

I got it when updating a kong helm chart to a newer version.

There are definitely not duplicated keys in the values passed to the chart /:

[djcristi]

such support from Lens. no fix...

[timoa]

I have the same issue, but I don't know if it's because I'm updating the Kube API to upgrade Kube to the latest and the current Helm/Kube cannot read the new API version. I will see if that's the case after the update.

We still have access to the rollback popup with the three dots menu, but we can't see the Helm chart or edit it with Lens

Helm is not showing any issues on the Helm chart deployed.