I running istio 1.3 . Created with helm chat istio igreess gw in namespace test. If I put the istio ingress gw in some another name space ( rather that istio-system) I got in the istio-proxy log: Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected . Did someone encounter this problem? If I run istioctl proxy-status the envoy is not in the list.
Try killing the Ingress Gateway pod.
Seems this have been already mentioned on GitHub here and here.
Also you can try getting more information about the issue as it was mentioned by @GregHanson in his comment.
Also check the logs of the ingress gateway to see if it rejected a listener
kubectl logs -n istio-system -l istio=ingressgateway | grep -v deprecatedAlso verify which listeners the ingress gateway does know about:
istioctl proxy-config listeners <istio_ingressgateway_pod>.istio-systemThen, check the logs of istio-pilot for any errors related that may have occurred for the host/port defined in the Gateway.
kubectl logs -n istio-system <istio_pilot_pod> discovery