liveBook · Manning

Gateway api

As explained in Effective Platform Engineering

The Kubernetes Gateway API is a Kubernetes API standard for configuring traffic ingress and routing through role-oriented gateway resources.

The Kubernetes Gateway API is a standard for configuring traffic ingress and routing. Its role-oriented design lets developers manage the ingress elements affecting their applications while a platform provides the shared gateway infrastructure. section 8.4.2

A service mesh can provide these capabilities because its control plane manages the proxies that route traffic to applications. This makes ingress part of a shared integration point that can also support traffic control, resiliency, and security. Introduce those capabilities as the platform needs them rather than requiring every proxy feature from the start. section 8.4.2

Platform-managed ingress

A platform can deploy Istio to provide a self-service ingress experience backed by managed domain names. An illustrated application route uses an Istio VirtualService; that resource is an Istio-specific example, not a Gateway API resource. section 8.4.2

How Effective Platform Engineering covers it

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 it assumes
Assumes familiarity with Kubernetes applications and ingress; does not teach Gateway API configuration from zero.
What you can do after
Evaluate/understand it as an option for developer-managed ingress within a service-mesh-backed platform.
How it connects
Connects Gateway API to service meshes, proxy control planes, ingress, and traffic routing.

Also explained in

Compare how 3 books explain gateway api →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Effective Platform Engineering. The section links point to the parts of the book it draws on.