1

团队,当我尝试 istio-0.3.0 时,出现错误。有小费吗?谢谢!

$ kubectl apply -f <(istioctl kube-inject -f myservice.yaml) Error: could not read valid configmap "istio" from namespace "istio- system": failed to convert to proto. unknown field "controlPlaneAuthPolicy" in istio_proxy_v1_config.ProxyConfig - Re-run kube-inject with-i 并确保存在有效的 MeshConfig 错误:没有传递给应用的对象`但是我检查了,configmap 就在命名空间“istio-system”中

$ kubectl get configmap -n istio-system NAME DATA AGE istio 1 2m istio-ingress-controller-leader-istio 0 2m istio-mixer 1 2m 仅供参考,我在那之前做了什么 curl -L https://git.io/getLatestIstio | sh - cd istio-0.3.0 kubectl apply -f install/kubernetes/istio-auth.yaml namespace "istio-system" created clusterrole "istio-pilot-istio-system" created clusterrole "istio-initializer-istio-system" created clusterrole "istio-mixer-istio-system" created clusterrole "istio-ca-istio-system" created clusterrole "istio-sidecar-istio-system" created clusterrolebinding "istio-pilot-admin-role-binding-istio-system" created clusterrolebinding "istio-initializer-admin-role-binding-istio-system" created clusterrolebinding "istio-ca-role-binding-istio-system" created clusterrolebinding "istio-ingress-admin-role-binding-istio-system" created clusterrolebinding "istio-sidecar-role-binding-istio-system" created clusterrolebinding "istio-mixer-admin-role-binding-istio-system" created configmap "istio-mixer" created service "istio-mixer" created serviceaccount "istio-mixer-service-account" created deployment "istio-mixer" created customresourcedefinition "rules.config.istio.io" created customresourcedefinition "attributemanifests.config.istio.io" created customresourcedefinition "deniers.config.istio.io" created customresourcedefinition "listcheckers.config.istio.io" created customresourcedefinition "memquotas.config.istio.io" created customresourcedefinition "noops.config.istio.io" created customresourcedefinition "prometheuses.config.istio.io" created customresourcedefinition "stackdrivers.config.istio.io" created customresourcedefinition "statsds.config.istio.io" created customresourcedefinition "stdios.config.istio.io" created customresourcedefinition "svcctrls.config.istio.io" created customresourcedefinition "checknothings.config.istio.io" created customresourcedefinition "listentries.config.istio.io" created customresourcedefinition "logentries.config.istio.io" created customresourcedefinition "metrics.config.istio.io" created customresourcedefinition "quotas.config.istio.io" created customresourcedefinition "reportnothings.config.istio.io" created attributemanifest "istioproxy" created attributemanifest "kubernetes" created stdio "handler" created logentry "accesslog" created rule "stdio" created metric "requestcount" created metric "requestduration" created metric "requestsize" created metric "responsesize" created metric "tcpbytesent" created metric "tcpbytereceived" created prometheus "handler" created rule "promhttp" created rule "promtcp" created configmap "istio" created customresourcedefinition "destinationpolicies.config.istio.io" created customresourcedefinition "egressrules.config.istio.io" created customresourcedefinition "routerules.config.istio.io" created service "istio-pilot" created serviceaccount "istio-pilot-service-account" created deployment "istio-pilot" created service "istio-ingress" created serviceaccount "istio-ingress-service-account" created deployment "istio-ingress" created serviceaccount "istio-ca-service-account" created deployment "istio-ca" created

4

1 回答 1

1

我怀疑您曾经安装过以前版本的 istio,因此您istioctl仍然指的是旧版本。要确认这一点:是否istioctl version打印出版本 0.3.0?

getLatestIstio脚本实际上并没有安装到您的 $PATH 中,它存在于istio-0.3.0/bin. 请运行您的命令,如kubectl apply -f <(./bin/istioctl kube-inject -f myservice.yaml).

于 2017-12-15T18:17:46.733 回答