Skip to content

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

@amitlin

Description

@amitlin

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?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions