Skip to content

Instantly share code, notes, and snippets.

@houstondapaz

houstondapaz/fixing-helm.md

Created May 31, 2021 21:24
Show Gist options
  • Save houstondapaz/fbbecf5138c3a6760ef77b986bcb8a1e to your computer and use it in GitHub Desktop.
Save houstondapaz/fbbecf5138c3a6760ef77b986bcb8a1e to your computer and use it in GitHub Desktop.
Download ZIP
Raw
fixing-helm.md

In Helm 2, changing the release status to deployed lets you bypass the issue:

kubectl -n kube-system patch configmap [release name].[release version] --type=merge -p '{"metadata":{"labels":{"STATUS":"DEPLOYED"}}}'

Where:

  • release name is the name of the release you want to update.
  • release version is the current version of your release.

Note: Keep in mind that the solution above only serves to bypass the issue. You still need to make manual adjustments to add the missing resources.

Since Helm 3 stores the deployment history as Kubernetes secrets, use the following command to change the deployment status:

kubectl -n app-namespace patch secret [release name].[release version] --type=merge -p '{"metadata":{"labels":{"status":"deployed"}}}'

Original link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment