Interview › Istio & Service Mesh
What is the Kubernetes Gateway API, and how is Istio adopting it?
Istio & Service Mesh · Intermediate level
Answer
The Kubernetes Gateway API is a standardized Kubernetes networking API intended to be more expressive and role-oriented than Ingress. It introduces resources such as GatewayClass, Gateway, and route types. Istio supports it as a way to configure ingress and mesh traffic with standard Kubernetes APIs.
Technical explanation
GatewayClass represents the implementation type, such as Istio.
Gateway represents listener infrastructure and allowed route attachment.
HTTPRoute or TCPRoute represents application routing rules that attach to a Gateway.
Hands-on example
Gateway API sketch:
kind: Gateway
metadata:
name: public
spec:
gatewayClassName: istio
listeners:
- name: https
port: 443
protocol: HTTPS
---
kind: HTTPRoute
spec:
parentRefs:
- name: public
rules:
- backendRefs:
- name: checkout
port: 8080Preparing for an interview?
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 a service mesh, and what problem does it solve?
- 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?