Cannot download remote chart on render

[abrekhov]

Before proceeding

• I didn't find a similar issue

Version

1.16.0

How to reproduce

export NELM_CHART_REPO_URL="https://charts.bitnami.com/valkey"
export NELM_CHART_VERSION="5.0.4"
export NELM_FEAT_REMOTE_CHARTS=true
export NELM_VALUES=<path_to_values>
export NELM_RELEASE=valkey
export NELM_NAMESPACE=default
nelm release plan install

Result

nelm release plan install
Planning release install "redis-sentinel-test" (namespace: "default")
Error: release plan install: render chart: download chart "": download chart "oci://registry-1.docker.io/bitnamicharts/valkey:5.0.4": invalid_reference: invalid tag

# check
helm pull oci://registry-1.docker.io/bitnamicharts/valkey:5.0.4
Pulled: registry-1.docker.io/bitnamicharts/valkey:5.0.4
Digest: sha256:b9daeee84d1bf4044afb767bdcfcf238aeb88861727cea839746ea78ca308a8c

Expected result

Valid plan

Additional information

No response

[ilya-lesikov]

Helm issue: helm/helm#13466
Will fix

[ilya-lesikov]

Well, looking at this, it seems like it's going to be easier to just migrate to Helm v4 in Nelm. Which we going to do in half a year max.

Can you try this workaround for now? helm/helm#13466 (comment)

[abrekhov]

export NELM_CHART_REPO_URL="oci://registry-1.docker.io/bitnamicharts/valkey"
nelm release plan install valkey-test
Planning release install "redis-sentinel-test" (namespace: "default")
Error: release plan install: render chart: download chart "": construct chart downloader: get chart URL: looks like "oci://registry-1.docker.io/bitnamicharts/valkey" is not a valid chart    ↵
repository or cannot be reached: object required

export NELM_CHART_REPO_URL="oci://registry-1.docker.io/bitnamicharts"
nelm release plan install valkey-test
Planning release install "redis-sentinel-test" (namespace: "default")
Error: release plan install: render chart: download chart "": construct chart downloader: get chart URL: looks like "oci://registry-1.docker.io/bitnamicharts" is not a valid chart           ↵
repository or cannot be reached: object required

[ilya-lesikov]

Should work:

export NELM_FEAT_REMOTE_CHARTS=true
nelm release plan install -n myns -r myrls oci://registry-1.docker.io/bitnamicharts/valkey --chart-version 5.0.4

[abrekhov]

nelm version 1.16.0

export NELM_FEAT_REMOTE_CHARTS=true
nelm release plan install -n myns -r myrls oci://registry-1.docker.io/bitnamicharts/valkey --chart-version 5.0.4
Planning release install "myrls" (namespace: "myns")
Error: release plan install: render chart: download chart "": construct chart downloader: get chart URL: looks like "oci://registry-1.docker.io/bitnamicharts/valkey" is not a valid chart    ↵
repository or cannot be reached: object required

[ilya-lesikov]

No u

Unset all other env vars, might be the problem

[abrekhov]

unset NELM_CHART_REPO_URL

helped! Thanks.
But it would be nice (especially for CI) to manage the release only with env vars and just exec nelm release (plan) install with no args for both local and remote charts.

PS: making CI component for gitlab ci.

[ilya-lesikov]

Yes, currently command args can't be set via env vars. We'll think on it, might be useful.

[ilya-lesikov]

Though nothing prevents you from

export CHART=oci://...
nelm release plan install $CHART

[abrekhov]

Though nothing prevents you from

export CHART=oci://...
nelm release plan install $CHART

But it works differently with https and oci repositories:

The --chart-version flag works for OCI charts but not for HTTPS charts.

OCI format - works:

nelm release plan install -n ns -r release oci://registry-1.docker.io/bitnamicharts/valkey --chart-version 4.1.3

HTTPS format - doesn't work:

# This fails with 403 Forbidden
nelm release plan install -n ns -r release https://charts.bitnami.com/bitnami/nginx --chart-version 17.2.1

# Only full URL with version in filename works
nelm release plan install -n ns -r release https://charts.bitnami.com/bitnami/nginx-17.2.1.tgz

What would supper nice is to avoid nelm repo add for both oci and https remote charts, have env vars to configure plan/install.

Something like that:

# OCI (already works)
nelm release plan install -n ns -r release oci://registry/chart --chart-version X.Y.Z

# HTTPS (should work the same way)
nelm release plan install -n ns -r release https://charts.example.com/repo/chart --chart-version X.Y.Z

Or :

# HTTPS 
nelm release plan install -n ns -r release https://charts.example.com/repo/chart-X.Y.Z.tgz
# OCI
nelm release plan install -n ns -r release oci://registry/chart:X.Y.Z

PS: I think last approach is better, because helm pull oci://registry/chart:X.Y.Z is working