Make helm charts argocd compatible

[MikeMichel]

Deploying crds with argocd fails with: Unable to create application: application spec for elemental-operator is invalid: InvalidSpecError: Unable to generate manifests in : rpc error: code = Unknown desc = failed to walk for symlinks in /tmp/c880912f-9793-440b-a347-ca96b8307b6a/elemental-operator-crds-chart: lstat /tmp/c880912f-9793-440b-a347-ca96b8307b6a/elemental-operator-crds-chart: no such file or directory

This is because argocd untars the charts tgz and expects a subfolder with the same name as the chart itself defined in the config:

  source:
    repoURL: registry.suse.com/rancher
    targetRevision: 1.5.4
    chart: elemental-operator-crds-chart

But extractingelemental-operator-crds-chart-1.5.4.tgz creates a folder named elemental-operator-crds so the -chart part is missing and argocd fails.

Same for the operator chart.

[kkaempf]

Good catch, thanks for reporting this.

[kkaempf]

Thinking about this, we're not sure if this is an Elemental or an ArgoCD bug. 🤔

Helm seems to be happy with the Charts as they are.

@MikeMichel do you have any references about ArgoCD's naming policy ?

[MikeMichel]

Afaik there is no naming policy. I guess they expect the packaging is done with helm package where the name of the created tgz is the same like name in Chart.yaml or to be precise CHART_NAME-VERSION.tgz

[davidcassany]

Following Rancher conventions we could consider renaming the charts as:

• elemental-operator-chart -> elemental
• elemental-opertaor-crds-chart -> elemental-crd

That way we would also align with marketplace charts.