Interview › Istio & Service Mesh
How do Istio Gateways relate to the Kubernetes Gateway API?
Istio & Service Mesh · Intermediate level
Answer
Istio Gateways are Istio's native API for configuring gateway proxies. The Kubernetes Gateway API is a broader Kubernetes standard for Gateway, HTTPRoute, TCPRoute, and related resources. Istio supports Gateway API so teams can use a more portable and role-oriented model.
Technical explanation
The Istio Gateway API usually pairs Gateway with VirtualService.
The Kubernetes Gateway API separates infrastructure ownership of Gateways from application ownership of Routes.
This separation is helpful in multi-team platforms where platform teams own shared gateways and app teams own route attachments.
Hands-on example
Ownership model:
Platform team applies Gateway in infra namespace.
App team applies HTTPRoute in app namespace with parentRefs to that Gateway.
CI checks allowed hostnames and namespaces before merge.
This reduces accidental edits to a shared Istio Gateway object.
Check how well your resume matches the role with our free resume checker— match score, ATS check, and the skills you're missing.
More Istio & Service Mesh interview questions
- What is Istio, and what are the core capabilities it provides?
- What is the difference between the Istio control plane and data plane?
- What is istiod, and what does it do?
- What is Envoy, and what role does it play in Istio?
- What is the sidecar pattern, and how does Istio inject the proxy?
- How does automatic sidecar injection work (namespace label, webhook)?
- What is the Istio ambient (sidecarless) mode, and how does it differ from sidecar mode?
- What is the difference between ztunnel and a waypoint proxy in ambient mode?