Istio Ingress Gateway
An Ingress Gateway acts as an edge load balancer for your service mesh, handling incoming HTTP/TCP traffic. It exposes ports and protocols, but unlike Kubernetes Ingress, it does not include routing rules—that’s delegated to a VirtualService.A Gateway only configures the listener. Use a VirtualService to define how traffic is routed.
Istio VirtualService
A VirtualService lets you define routing rules that map incoming requests (from a Gateway or internal service) to destinations in the mesh.
httpbin.example.com to the httpbin service on port 8000.
Exposing the DevSecOps Application
Our applicationdevsecops-svc is currently a ClusterIP service on port 8080 in the prod namespace:
Create Gateway + VirtualService for prod
Create both resources in a single manifest (istio-gateway-vs.yaml):
Access via Istio Ingress Gateway
Istio’sistio-ingressgateway Service is typically a LoadBalancer or NodePort. In this environment it’s exposed on NodePort 32564:
/ and /increment are reachable through the Gateway.
Restricting Paths with VirtualService
To disable the root path (/) externally, remove or comment out the exact-match rule:
Viewing Configuration in Kiali
Kiali provides a UI for inspecting Istio resources.

