Gateway api
The Kubernetes Gateway API is a networking standard for defining gateways, listeners, and traffic routing between external clients and cluster services.
Kubernetes in Action, Second Edition
The Gateway API is a Kubernetes networking API standard for defining traffic gateways, listeners, and routing between external clients and cluster services.
- How it is used
- Exposes Kubernetes Services to external clients through gateway proxies and protocol-specific routes.
- How deep it goes
- Works through GatewayClass, Gateway, and Route configuration, testing, and status checks; notes that features depend on the installed provider.
- Examples
- Uses Istio Gateway and HTTPRoute manifests, kubectl inspection, curl requests, and TCP and UDP listener examples.
- What you can do after
- Operate/configure it to expose Services through listeners and routes, then diagnose attachment or provider-support problems from route status.
Read how Kubernetes in Action, Second Edition explains gateway api →
Effective Platform Engineering
The Kubernetes Gateway API is a Kubernetes API standard for configuring traffic ingress and routing through role-oriented gateway resources.
- How it is used
- Positions the Gateway API as a standard for developer-managed application ingress on Kubernetes.
- How deep it goes
- Explains its platform role and mesh relationship, but does not work through Gateway API resource configuration.
- Examples
- Illustrates self-service ingress with an Istio-based platform and an Istio VirtualService route.
- What you can do after
- Evaluate/understand it as an option for developer-managed ingress within a service-mesh-backed platform.
Read how Effective Platform Engineering explains gateway api →
Acing the Certified Kubernetes Administrator Exam, Second Edition
Gateway API is a Kubernetes networking API for expressing and implementing traffic routing through gateway resources.
- How it is used
- Manages ingress traffic while dividing infrastructure, gateway operation, and application routing into separate responsibilities.
- How deep it goes
- Works through three resource manifests and an HTTPRoute check, but does not demonstrate controller installation or end-to-end traffic verification.
- Examples
- Uses kubectl manifests for a GatewayClass, HTTP Gateway listener, and hostname-and-path HTTPRoute targeting an nginx backend.
- What you can do after
- Apply it via kubectl by configuring GatewayClass, Gateway, and HTTPRoute resources and checking that the HTTPRoute appears.
Read how Acing the Certified Kubernetes Administrator Exam, Second Edition explains gateway api →
Related concepts
- HTTPRoutehas part · An HTTPRoute is a Kubernetes Gateway API resource defining how HTTP requests are matched and forwarded to backend services through parent gateways.
- ingress objectalternative to · A Kubernetes Ingress is an API resource that specifies rules for routing external HTTP and HTTPS requests to services within a cluster.
- gatewayclasshas part · A GatewayClass is a cluster-scoped Kubernetes Gateway API resource defining a class of gateways managed by a particular controller.
- gateway objecthas part · A Kubernetes Gateway API Gateway is a resource that defines a network entry point and specifies its implementation class, listeners, and traffic protocols or ports.
- gateway api implementationimplemented by · A Gateway API implementation is software installed in a Kubernetes cluster that realizes Gateway API resources and provisions the traffic proxies they require.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.