istio: Can't install v1.3.3 with helm v2.15.0

Bug description The installation works fine with helm v2.14.3

$ helm version Client: &version.Version{SemVer:“v2.15.0”, GitCommit:“c2440264ca6c078a06e088a838b0476d2fc14750”, GitTreeState:“clean”} Server: &version.Version{SemVer:“v2.15.0”, GitCommit:“c2440264ca6c078a06e088a838b0476d2fc14750”, GitTreeState:“clean”}

$ helm install istio-1.3.3/install/kubernetes/helm/istio --name istio --namespace istio-system Error: release istio failed: Deployment.apps “istio-sidecar-injector” is invalid: spec.template.spec.affinity.nodeAffinity.requiredDuringSchedulingIgnoredDuringExecution.nodeSelectorTerms[0].matchExpressions[0].values: Required value: must be specified when operator is ‘In’ or ‘NotIn’

Affected product area (please put an X in all that apply)

[ ] Configuration Infrastructure [ ] Docs [*] Installation [ ] Networking [ ] Performance and Scalability [ ] Policies and Telemetry [ ] Security [ ] Test and Release [ ] User Experience [ ] Developer Infrastructure

Expected behavior

Steps to reproduce the bug

Version (include the output of istioctl version --remote and kubectl version) $ kubectl version Client Version: version.Info{Major:“1”, Minor:“16”, GitVersion:“v1.16.2”, GitCommit:“c97fe5036ef3df2967d086711e6c0c405941e14b”, GitTreeState:“clean”, BuildDate:“2019-10-15T19:18:23Z”, GoVersion:“go1.12.10”, Compiler:“gc”, Platform:“linux/amd64”} Server Version: version.Info{Major:“1”, Minor:“16”, GitVersion:“v1.16.2”, GitCommit:“c97fe5036ef3df2967d086711e6c0c405941e14b”, GitTreeState:“clean”, BuildDate:“2019-10-15T19:09:08Z”, GoVersion:“go1.12.10”, Compiler:“gc”, Platform:“linux/amd64”} How was Istio installed?

Environment where bug was observed (cloud vendor, OS, etc)

Additionally, please consider attaching a cluster state archive by attaching the dump file to this issue.

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Reactions: 11
  • Comments: 22 (5 by maintainers)

Most upvoted comments

Just ran into this today as well … appears the issue is isolated to the latest helm release. I confirmed installing helm 2.13 works. All templates generate fine. The issue seems to be that with helm 2.15 the “Values” for node affinity do NOT get populated. Thus you end up with a failure to apply the deployment manifests.

Quick fix for now is a downgrade of Helm.

Cheers!

The workaround is using helm 2.14.3, if you run in to helm init problem with k8s v1.16, use this workaround:

helm init --service-account tiller --output yaml | sed 's@apiVersion: extensions/v1beta1@apiVersion: apps/v1@' | sed 's@  replicas: 1@  replicas: 1\n  selector: {"matchLabels": {"app": "helm", "name": "tiller"}}@' | kubectl apply -f -

I’m on Helm 3 now, and both 1.3.4 and 1.4.0 install fine.

@dumindu What’s your k8s and helm version? What’s the output of helm init --output json? Check this workaround: https://github.com/helm/helm/issues/6374#issuecomment-533185074