Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Add capability to redeploy helm charts without failure

See original GitHub issue

Problem Statement Helm deployments cannot be deployed idempotently.

Expected Behavior Re-running pulumi up on a stack with Helm charts should not fail if the chart already exists on the cluster. Alternatively this could be a flag/option.

Current Behavior Re-running pulumi up generates errors like this… error: Plan apply failed: 1 error occurred: * secrets "alertmanager-kube-prometheus" already exists

Notes Helm has this capability using helm upgrade --install This will fail if the chart exists in a FAILED release state. To fix this use the --force flag.

It would be nice to have upgrade/force as options in Pulumi helm to mimic this behavior.

Issue Analytics

State:
Created 5 years ago
Comments:18 (11 by maintainers)

Top GitHub Comments

1reaction

joeduffycommented, Sep 20, 2018

Rereading @carterwilliamson’s bug description, I want to ask a clarifying question:

Re-running pulumi up on a stack with Helm charts should not fail if the chart already exists on the cluster. Alternatively this could be a flag/option.

Did the Helm chart get installed through other means already, before running pulumi up? (Instead of, say, pulumi up failing when run a second time for an existing stack containing a Helm Chart.) And what you’re wanting is a way for the pulumi up to detect this, akin to a helm upgrade --install, rather than it failing as it does today with the error message you’ve shown?

After rereading, particularly this part

It would be nice to have upgrade/force as options in Pulumi helm to mimic this behavior.

I am suspecting this is what you meant, rather than a naming collision due to a bug in Pulumi, etc.

If yes, this definitely seems like a reasonable thing to support, perhaps with an upgrade?: boolean option that can be passed to the Helm Chart constructor.

0reactions

hausdorffcommented, Apr 9, 2019

Per @cleverguy25 and @eshamay, the fix provided does work and we can close this out.

Top Results From Across the Web

13 Best Practices for using Helm - Coder Society

This article features 13 best practices for creating Helm charts to manage your applications running in Kubernetes.

Chart Development Tips and Tricks - Helm

This guide covers some of the tips and tricks Helm chart developers have learned while building production-quality charts. Know Your Template Functions. Helm ......

helm3 - upgrade does not refresh pod with force

I tried using 'helm upgrade --install --force ....' as suggested in helm3 upgrade documentation but it fails with below error in Jenkins log....

How to fix Helm's "Upgrade Failed: has no deployed releases ...

Change its value to deployed, then reuse your "helm upgrade --install" command and it will works ! Use a Kubernetes command. You can...

HELM Best practices · Codefresh | Docs

While this workflow is very flexible, it adds complexity on the number of Helm charts available (since they exist in multiple Helm repositories)....