安装istio 1.0.3后无法与服务进行交互

时间:2018-11-02 09:50:20

标签: istio

我使用了 istio-1.1.0-snapshot.2 ,并且一切正常。然后,我将 istio升级到istio-1.0.3。,之后我无法与Mesh中的服务进行交互。

在istio-ingressgateway的日志中,我看到了这样的问题:

[2018-10-28 09:18:41.317][20][info][main] external/envoy/source/server/drain_manager_impl.cc:63] shutting down parent after drain
[2018-10-28 09:19:35.188][34][info][main] external/envoy/source/server/drain_manager_impl.cc:63] shutting down parent after drain
[2018-10-28 09:19:35.189][20][info][main] external/envoy/source/server/hot_restart_impl.cc:444] shutting down due to child request
[2018-10-28 09:19:35.189][20][warning][main] external/envoy/source/server/server.cc:373] caught SIGTERM
[2018-10-28 09:19:35.189][20][info][main] external/envoy/source/server/server.cc:436] main dispatch loop exited
[2018-10-28 09:19:35.197][20][info][main] external/envoy/source/server/server.cc:472] exiting

[2018-11-02 09:22:33.045][34][warning][upstream] external/envoy/source/common/config/grpc_mux_impl.cc:240] gRPC config stream closed: 13,
[2018-11-02 09:22:43.322][34][warning][upstream] external/envoy/source/common/config/grpc_mux_impl.cc:240] gRPC config stream closed: 14, upstream connect error or disconnect/reset before headers
[2018-11-02 09:22:53.503][34][warning][upstream] external/envoy/source/common/config/grpc_mux_impl.cc:240] gRPC config stream closed: 14, upstream connect error or disconnect/reset before headers
[2018-11-02 09:23:05.420][34][warning][upstream] external/envoy/source/common/config/grpc_mux_impl.cc:240] gRPC config stream closed: 14, upstream connect error or disconnect/reset before headers
[2018-11-02 09:23:15.810][34][warning][upstream] external/envoy/source/common/config/grpc_mux_impl.cc:240] gRPC config stream closed: 14, upstream connect error or disconnect/reset before headers

执行命令istioctl proxy-status之后,我已经看到,如果是1.0.2,我的副车代理版本将是

有什么建议吗?

2 个答案:

答案 0 :(得分:0)

升级Istio控制平面后,需要升级Sidecar容器。简而言之,您需要重新注入它们。

如果使用手动注入,则可以通过以下命令对其进行升级:

$ kubectl apply -f <(istioctl kube-inject -f $ORIGINAL_DEPLOYMENT_YAML)

如果您使用自动边车注入,则可以通过对所有吊舱进行滚动更新来升级边车,以便新版本的边车将自动重新注入。

这是文档上的link

答案 1 :(得分:0)

1.0.3似乎已损坏,它不会在容器之间路由请求。即使是简单的wordpress / mysql网站也无法在1.0.3版中运行