IstioIngressGateway and Virtual Service with custom TCP Ports

1

IstioIngressGateway and Virtual Service with custom TCP Ports.

I have deployed my TCP Server as service in my Azure Kubernetes Cluster.

I have downloaded the istio package. I have modifed the install\kubernetes\helm\istio\values-istio-gateways.yaml with my TCP ports. And then i have deployed the istio under istio-system namespace. All the services are up and running.

issue#1: Under istio-ingressgateway service, i don’t see my custom TCP ports.

issue#2: Since i don’t see my TCP ports,I have modified the istio-ingressgateway pod using the command - (kubectl edit svc istio-ingressgatewayXYZ -n istio-system), and i have added my ports saved the file. I have created the Virtual Service, by adding the source port/Host and destination port(my TCP service port). When i try to access the istiogateway with my tcp ports, i am unable to hit. I see that i can hit the default https ports like 80 and 443. I tried from the TCP client and and also from curl command.

Please anyone can answer my question, what could be the reason, and if you know any solution for this issue let me know.

2

How did you deploy Istio? Can you share the steps?

3

I am facing the same issue, I tested the tcp-echo sample and found the port 31400 defined in Gateway was not added to the istio-ingressgateway service.