Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New images not pulled after switching to spec.valuesObject #17842

Closed
3 tasks done
ro0NL opened this issue Apr 15, 2024 · 1 comment
Closed
3 tasks done

New images not pulled after switching to spec.valuesObject #17842

ro0NL opened this issue Apr 15, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@ro0NL
Copy link

ro0NL commented Apr 15, 2024

Checklist:

  • I've searched in the docs and FAQ for my answer: https://bit.ly/argocd-faq.
  • I've included steps to reproduce the bug.
  • I've pasted the output of argocd version.

Describe the bug

We are trying to migrate from values: | to valuesObject: as per https://argo-cd.readthedocs.io/en/stable/user-guide/helm/#values

When a new image is built the image updater shows following log:

helm template . --name-template some --namespace some --kube-version 1.27 \
--set-string apps.api.image.repository=some \
--set-string apps.api.image.tag=some <api versions removed> --include-crds` failed exit status 1:
Error: template: chart/file.yaml:22:17: executing \"chart/file.yaml\" at <$app.webserver.upstream>: nil pointer evaluating interface {}.upstream%0A%0A

Expected behavior

Expected is the new image being updated. However it seems the existing chart becomes incompatible when switching to valuesObject:, and im wondering how we should proceed.

Chart snippet (unchanged)

data:
  api.conf: |
    {{- with $app.webserver.upstream }}
    upstream backend {
      {{- . | nindent 6 }}
    }
    {{- end }}

Nested value (unchanged)

valuesObject: # values: |
    apps:
        api:
            webserver:
                upstream: |
                    multi
                    line

Version

argocd: v2.10.0+2175939
  BuildDate: 2024-02-06T14:47:59Z
  GitCommit: 2175939ed6156ddd743e60f427f7f48118c971bf
  GitTreeState: clean
  GoVersion: go1.21.6
  Compiler: gc
  Platform: linux/amd64
argocd-server: v2.10.4+f5d63a5
  BuildDate: 2024-03-18T08:09:23Z
  GitCommit: f5d63a5c77d2e804e51ef94bee3db441e0789d00
  GitTreeState: clean
  GoVersion: go1.21.3
  Compiler: gc
  Platform: linux/amd64
  Kustomize Version: v5.2.1 2023-10-19T20:13:51Z
  Helm Version: v3.14.3+gf03cc04
  Kubectl Version: v0.26.11
  Jsonnet Version: v0.20.0
@ro0NL ro0NL added the bug Something isn't working label Apr 15, 2024
@ro0NL
Copy link
Author

ro0NL commented Apr 15, 2024

Found the correct repo, it's a known bug; argoproj-labs/argocd-image-updater#692

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant