Chart doesn't work with kustomize because of lookup use

[ashtonian]

Kustomize seems to fail with valid values setting because of lookup use, argo does the same.

kustomize build . --enable-helm --debug                                    (main|✔)
Error: unknown flag: --debug
ashtonian@Mac harbor % kustomize build . --enable-helm                                            (main|✔)
Error: Error: template: harbor/templates/trivy/trivy-sts.yaml:29:28: executing "harbor/templates/trivy/trivy-sts.yaml" at <include (print $.Template.BasePath "/trivy/trivy-secret.yaml") .>: error calling include: template: harbor/templates/trivy/trivy-secret.yaml:11:15: executing "harbor/templates/trivy/trivy-secret.yaml" at <include "harbor.redis.urlForTrivy" .>: error calling include: template: harbor/templates/_helpers.tpl:239:48: executing "harbor.redis.urlForTrivy" at <include "harbor.redis.url" $>: error calling include: template: harbor/templates/_helpers.tpl:207:64: executing "harbor.redis.url" at <include "harbor.redis.cred" $>: error calling include: template: harbor/templates/_helpers.tpl:196:25: executing "harbor.redis.cred" at <include "harbor.redis.pwdfromsecret" $>: error calling include: template: harbor/templates/_helpers.tpl:190:56: executing "harbor.redis.pwdfromsecret" at <.Values.redis.external.existingSecret>: nil pointer evaluating interface {}.REDIS_PASSWORD

Use --debug flag to render out invalid YAML
: unable to run: 'helm template harbor /Users/ashtonian/projects/hops/k8s/dev/harbor/charts/harbor-1.17.0/harbor --namespace dev -f /var/folders/jv/f_n4zzr921z8qjd2_nb6ns500000gn/T/kustomize-helm-1169992686/harbor-kustomize-values.yaml --include-crds' with env=[HELM_CONFIG_HOME=/var/folders/jv/f_n4zzr921z8qjd2_nb6ns500000gn/T/kustomize-helm-1169992686/helm HELM_CACHE_HOME=/var/folders/jv/f_n4zzr921z8qjd2_nb6ns500000gn/T/kustomize-helm-1169992686/helm/.cache HELM_DATA_HOME=/var/folders/jv/f_n4zzr921z8qjd2_nb6ns500000gn/T/kustomize-helm-1169992686/helm/.data] (is 'helm' installed?): exit status 1
ashtonian@Mac harbor %

[MinerYang]

It is a known issue from upstream helm while using dry run to render the manifest
#1641

We will keep tracking the issue and take some time to see if there's any improvement could be done here.

Best,
Miner

[github-actions]

This issue is being marked stale due to a period of inactivity. If this issue is still relevant, please comment or remove the stale label. Otherwise, this issue will close in 30 days.

[EdwardCooke]

One improvement to support Argo, and this Helm chart is making it so we can tell the helm chart to use an existing secret. That way we can create that secret using something like cert manager for tls, and sealed secrets for all of the other secrets.

[EdwardCooke]

Also, here's my Argo app to ignore the differences of those pesky auto generated fields

apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
  annotations:
    argocd.argoproj.io/sync-wave: "-20"
  name: harbor
spec:
  destination:
    name: in-cluster
    namespace: harbor
  project: infrastructure
  source:
    path: kubernetes/harbor
    repoURL: xxx
    targetRevision: main
  syncPolicy:
    syncOptions:
    - CreateNamespace=true
    - ServerSideApply=false
  ignoreDifferences:
  - group: apps
    kind: Deployment
    jqPathExpressions:
    - .spec.template.metadata.annotations["checksum/configmap"]
    - .spec.template.metadata.annotations["checksum/secret"]
    - .spec.template.metadata.annotations["checksum/secret-core"]
    - .spec.template.metadata.annotations["checksum/secret-jobservice"]
  - group: ""
    kind: Secret
    name: harbor-core
    jqPathExpressions:
    - .data.CSRF_KEY
    - .data.secret
    - .data["tls.crt"]
    - .data["tls.key"]
  - group: ""
    kind: Secret
    name: harbor-jobservice
    jqPathExpressions:
    - .data.JOBSERVICE_SECRET
  - group: ""
    kind: Secret
    name: harbor-registry
    jqPathExpressions:
    - .data.REGISTRY_HTTP_SECRET
  - group: ""
    kind: Secret
    name: harbor-registry-htpasswd
    jqPathExpressions:
    - .data.REGISTRY_HTPASSWD

[github-actions]

This issue is being marked stale due to a period of inactivity. If this issue is still relevant, please comment or remove the stale label. Otherwise, this issue will close in 30 days.

[github-actions]

This issue was closed because it has been stalled for 30 days with no activity. If this issue is still relevant, please re-open a new issue.