istio: Unable to access the Kubernetes apiserver when injecting the istio_proxy sidecar
When I inject the istio_proxy sidecar, my pod’s main container which needs to access the Kubernetes apiserver can’t reach it and receives socket errors:
fleet/svc/index/service/service.go:49: Failed to list *v1beta1.Ingress: Get https://10.0.0.1:443/apis/extensions/v1beta1/namespaces/fleet/ingresses?resourceVersion=0: dial tcp 10.0.0.1:443: getsockopt: connection refused
Here are some error logs from the istio_proxy sidecar:
[2017-11-08 13:06:45.064][15][warning][config] external/envoy/source/server/listener_manager_impl.cc:248] error adding listener: 'tcp_172.17.0.13_9999' has duplicate address '172.17.0.13:9999' as existing listener
[2017-11-08 13:06:45.064][15][warning][upstream] external/envoy/source/server/lds_subscription.cc:65] lds: fetch failure: error adding listener: 'tcp_172.17.0.13_9999' has duplicate address '172.17.0.13:9999' as existing listener
The istio version used are:
- 0.2.10
- 0.2.12
The Kubernetes version is 1.7.5
About this issue
- Original URL
- State: closed
- Created 9 years ago
- Comments: 21 (4 by maintainers)
ohh okay @sterziev88. I haven’t got such problem yet and I also do have prometheus with istio and it works perfect. May be you can create an issue on istio regarding this, and may be someone can provide the solution.
@vaibhhavv Yes, I have istio-injection for that specific namespace and there are sidecars for all pods.
I resolve it as I added:
@sterziev88, It should not give any error after that atleast. 😦 I would sugest you to try the Istio
1.21with Kiali1.79.0and test if its the same case or not.@GregHanson I am still receiving errors of type:
with istio version 0.5.1.
Here is an example of the sidecar that was injected with
istioctl kube-inject: