helm: Helm install v2.14.0 "validation failed" error when using a template variable with value ""

Wouldn’t the prudent course of action to surface validation errors that were ‘silently’ failing before, with a warning ,that in a future release becomes an error? Or at the least, honor a force flag or some such that allows the user to choose how to handle it?

Any idea when v2.14.1 will be available?

This bit me today as well.

Hello Team, We are facing this issue in the newly released v3 as well but not in the beta version v3.0.0-beta.4. Kindly help with the resolution.

KubeCon EU, which is next week, not November. 😃

I can try #5643 tomorrow unless someone beats me to it.

Helm v2.14.1 has been released: https://github.com/helm/helm/releases/tag/v2.14.1

We’re backing out this change and cutting 2.14.1.

@SeriousM With any helm client version, you can use

helm init --tiller-namespace <namespace> --upgrade --canary-image

To get the latest helm client (master), you can use this : https://helm.sh/docs/using_helm/#from-canary-builds

For those that want to try the canary builds: https://helm.sh/docs/using_helm/#from-canary-builds

@fooka03 > Thanks for your reply! I didn’t understand previously that the fix would only apply to deployed charts being upgraded, and not new ones.

In my case unfortunately sticking to v2.13.1 isn’t an option either. 😦 The charts we created and that were working for v2.13.1 are provided to our users as part of a tool, and even though we would push a new version fixing this, we cannot force our users to use the latest version of our tool. Pushing a new version of the tool/charts might reduce the impact, but we’ll have in any case some of our users trying to install previous versions of our charts with Helm v2.14.0, and thus getting the validation error.

Even though I understand that my case is specific, isn’t this change going to also break some of the other charts that were generated previously (I’m thinking of https://github.com/helm/charts/tree/master/stable)?

If this is the case, would it be conceivable to postpone the validation change to Helm v3, and/or apply @StephanX’s suggestion above and display a warning for now?

this is still happening on v3.2.4. v3.2.3 works fine though.

@SeriousM With any helm client version, you can use

helm init --tiller-namespace <namespace> --upgrade --canary-image

To get the latest helm client (master), you can use this : https://helm.sh/docs/using_helm/#from-canary-builds

Thank you very much, I will try it out asap

Thank you @karuppiah7890 and @mitchellmaler Thanks for the tips! I remember I raised and issue to gitlab for autodevops. I will have to wait for the release of 2.4.1, don’t have the time right now to build a new pipeline 😦

@bacongobbler Sorry for the off-topic!

@SeriousM With any helm client version, you can use

helm init --tiller-namespace <namespace> --upgrade --canary-image

To get the latest helm client (master), you can use this : https://helm.sh/docs/using_helm/#from-canary-builds

This worked for me, thanks very much

The pull-request https://github.com/helm/helm/pull/5760 disabling the validation has been merged to master by @bacongobbler (thanks!). I assume that, as mentioned by @fooka03, the version 2.14.1 won’t be available before a couple of days but I wanted to share the good news. 😃

So it looks like #5643 does fix the manifest validation issue:

helm version
Client: &version.Version{SemVer:"v2.14.0", GitCommit:"05811b84a3f93603dd6c2fcfe57944dfa7ab7fd0", GitTreeState:"clean"}
Server: &version.Version{SemVer:"canary+unreleased", GitCommit:"9fb19967bab21ecb9748440a99487f2fb0560f63", GitTreeState:"clean"}

Release "belligerent-horse" has been upgraded.
LAST DEPLOYED: Fri May 17 10:32:12 2019
NAMESPACE: default
STATUS: DEPLOYED

RESOURCES:
==> v1/ConfigMap
NAME                             DATA  AGE
<redacted>-belligerent-horse  1     181d
<redacted>                      2     181d

==> v1/Pod(related)
NAME                               READY  STATUS       RESTARTS  AGE
<redacted>-belligerent-horse-0  1/1    Running      0         5m16s
<redacted>-belligerent-horse-1  1/1    Terminating  0         17h

==> v1/Service
NAME           TYPE       CLUSTER-IP  EXTERNAL-IP  PORT(S)   AGE
<redacted>  ClusterIP  None        <none>       8080/TCP  181d

==> v1/StatefulSet
NAME                             READY  AGE
<redacted>-belligerent-horse  2/2    181d

Still have to set any missing validation fields in the “new” templates of course, but it will at least let you deploy over existing releases.

Can we get an ETA for the hotfix? I really would like to avoid patching my server with a self-build helm/tiller. Thank you!