We’ve installed Istio 1.4.3 in kind of a “soft” way on our cluster. Meaning we don’t use the Istio gateway yet, but left traffic coming in over our Nginx ingress controller which was there from before we installed Istio.
We used the following command to create the manifest:
istioctl manifest generate \ --set values.gateways.istio-ingressgateway.sds.enabled=true \ --set values.global.k8sIngress.enabled=true \ --set values.global.k8sIngress.enableHttps=false \ --set values.global.k8sIngress.gatewayName=ingressgateway \ --set values.grafana.enabled=true \ --set values.kiali.enabled=true \ --set values.tracing.enabled=true
All things are working fine for HTTP traffic, but we are unable to get gRCP calls to work. We’re trying a simple service-2-service connection within the cluster using insecure mode (so no TLS yet).
What we do see is many many errors in the Envoy output:
[Envoy (Epoch 0)] [2020-01-21 18:06:00.646][warning][config] [bazel-out/k8-opt/bin/external/envoy/source/common/config/_virtual_includes/grpc_stream_lib/common/config/grpc_stream.h:91] gRPC config stream closed: 13,
These occur very frequently, sometimes every minute, sometimes somewhat longer in between.
Anyone with more in-depth knowledge have a clue as to what could be wrong? I’m guessing our config is note quite correct after all? It’s certainly interesting that HTTP traffic doesn’t seem to be affected and works just fine – but then again this traffic is coming from the outside and is not going service-2-service.
Any help or input would be appreciated!