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

Specifying -decode-kubernetes-secrets w/ --post-renderer during helm upgrade results in "X has no deployed releases" #234

Open
amitlin opened this issue Feb 21, 2024 · 1 comment

Comments

@amitlin
Copy link
Contributor

amitlin commented Feb 21, 2024

Issue

When integrating vals with helm using the --post-renderer approach, for some reason, while specifying -decode-kubernetes-secrets, helm fails to find the specified release.
i.e

helm upgrade --post-renderer vals --post-renderer-args eval --post-renderer-args -decode-kubernetes-secrets argocd .
Error: UPGRADE FAILED: "argocd" has no deployed releases

When adding the namespace using the --namespace, it works fine.

helm upgrade --post-renderer vals --post-renderer-args eval --post-renderer-args -decode-kubernetes-secrets argocd . --namespace argocd-ops
Release "argocd" has been upgraded. Happy Helming!
NAME: argocd
LAST DEPLOYED: Wed Feb 21 12:26:23 2024
NAMESPACE: argocd-ops
STATUS: deployed
REVISION: 70

I could find no apparent reason for this. Removing the -decode-kubernete-secrets flag and leaving only --post-renderer vals --post-renderer-args eval works perfectly. It's only once -decode-kubernetes-secrets is specified that this occurs.

Has anyone encountered this before? Am I doing something wrong?

@amitlin
Copy link
Contributor Author

amitlin commented Feb 21, 2024

I'd like to add that doing the equivalent with helm template works fine:

helm template . | vals eval -decode-kubernetes-secrets

the output is as expected

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant