istio: Cannot install helm charts successfully with release-1.1
Describe the bug
Install istio version release-1.1
with helm install --name istio --namespace istio-system . --tls --debug
here is output of kubectl get pod
NAME READY STATUS RESTARTS AGE
istio-citadel-8545986b5c-kpdb5 1/1 Running 0 6m
istio-egressgateway-7444f9bcf5-xkcfn 1/1 Running 0 6m
istio-galley-5c77f544cc-wg8ls 1/1 Running 0 6m
istio-ingressgateway-7fc4cdbfc7-bnxh8 1/1 Running 0 6m
istio-pilot-7974d67fcc-qwlv4 1/2 CrashLoopBackOff 6 6m
istio-policy-6bc68c8bcb-hcrk2 2/2 Running 0 6m
istio-sidecar-injector-74cd5c9565-x5n25 0/1 CrashLoopBackOff 6 6m
istio-telemetry-7658f85655-jj67m 2/2 Running 0 6m
jaeger-operator-7685bc6dff-ww4fc 1/1 Running 0 6d
prometheus-554b5cc795-rr8kb 1/1 Running 0 6m
the logs is
`kubectl logs -f istio-sidecar-injector-74cd5c9565-x5n25
2018-10-29T09:02:03.379156Z info FLAG: --caCertFile="/etc/istio/certs/root-cert.pem"
2018-10-29T09:02:03.379187Z info FLAG: --healthCheckFile="/health"
2018-10-29T09:02:03.379192Z info FLAG: --healthCheckInterval="2s"
2018-10-29T09:02:03.379197Z info FLAG: --help="false"
2018-10-29T09:02:03.379200Z info FLAG: --injectConfig="/etc/istio/inject/config"
2018-10-29T09:02:03.379202Z info FLAG: --kubeconfig=""
2018-10-29T09:02:03.379210Z info FLAG: --log_as_json="false"
2018-10-29T09:02:03.379212Z info FLAG: --log_caller=""
2018-10-29T09:02:03.379214Z info FLAG: --log_output_level="default:info"
2018-10-29T09:02:03.379216Z info FLAG: --log_rotate=""
2018-10-29T09:02:03.379220Z info FLAG: --log_rotate_max_age="30"
2018-10-29T09:02:03.379224Z info FLAG: --log_rotate_max_backups="1000"
2018-10-29T09:02:03.379227Z info FLAG: --log_rotate_max_size="104857600"
2018-10-29T09:02:03.379230Z info FLAG: --log_stacktrace_level="default:none"
2018-10-29T09:02:03.379240Z info FLAG: --log_target="[stdout]"
2018-10-29T09:02:03.379247Z info FLAG: --meshConfig="/etc/istio/config/mesh"
2018-10-29T09:02:03.379250Z info FLAG: --port="443"
2018-10-29T09:02:03.379252Z info FLAG: --tlsCertFile="/etc/istio/certs/cert-chain.pem"
2018-10-29T09:02:03.379255Z info FLAG: --tlsKeyFile="/etc/istio/certs/key.pem"
2018-10-29T09:02:03.379258Z info FLAG: --webhookConfigName="istio-sidecar-injector"
2018-10-29T09:02:03.379261Z info FLAG: --webhookName="sidecar-injector.istio.io"
2018-10-29T09:02:03.379273Z info version root@706809e7f5d6-docker.io/istio-master-20181020-09-15-bd24a62648c07e24ca655c39727aeb0e4761919a-Clean
Error: failed to create injection webhook failed to convert to proto. unknown field "policyCheckFailOpen" in v1alpha1.MeshConfig`
Expected behavior
Should be running normally. I have installed istio-1.1.0-snapshot.2
, it works well.
Steps to reproduce the bug
Version Client Version: version.Info{Major:“1”, Minor:“11”, GitVersion:“v1.11.0”, GitCommit:“91e7b4fd31fcd3d5f436da26c980becec37ceefe”, GitTreeState:“clean”, BuildDate:“2018-06-27T20:17:28Z”, GoVersion:“go1.10.2”, Compiler:“gc”, Platform:“darwin/amd64”} Server Version: version.Info{Major:“1”, Minor:“11”, GitVersion:“v1.11.1+icp-ee”, GitCommit:“5803c3b1f9422c43a963e0610b3a4cad565e127e”, GitTreeState:“clean”, BuildDate:“2018-09-04T09:29:02Z”, GoVersion:“go1.10.3”, Compiler:“gc”, Platform:“linux/amd64”}
Installation helm install --name istio --namespace istio-system . --tls --debug
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Reactions: 1
- Comments: 15 (11 by maintainers)
Commits related to this issue
- Current json-to-proto decoding does not recognize unknown fields and fails to load things like proxy mesh config, e.g. Error: failed to create injection webhook failed to convert to \ ... — committed to ayj/istio by ayj 6 years ago
- relax requirement for unknown fields in json-to-proto decoding (#9792) * Current json-to-proto decoding does not recognize unknown fields and fails to load things like proxy mesh config, e.g. ... — committed to istio/istio by ayj 6 years ago
Check the version of istioctl you have in your PATH. I think I saw this before, and it was because I had a istioctl that did not exactly match the istio distribution I was installing.
I Confirm, I got the same issue when upgrading from Istio 1.0.2 to 1.0.3. Resolved after updating istioctl to 1.0.3 in my path.