The Gateway API is a Kubernetes community standard for traffic management. It supports both Ingress-based north-south traffic management and Service Mesh-based east-west traffic management. This topic describes the core concepts of the Gateway API and north-south traffic solutions available in ACK.
Core concepts
The Gateway API uses a role-oriented, layered design that decouples infrastructure provisioning, cluster O&M, and application routing:
-
GatewayClass (Infrastructure layer): Like
IngressClass, defines the gateway controller type, such as ALB or Envoy Gateway, and general configurations. -
Gateway (O&M layer): Defines a gateway instance and its listener rules, such as ports, protocols, and TLS configurations.
-
HTTPRoute, GRPCRoute, and other route types (Application layer): Define traffic routing rules, such as path matching, header modification, and traffic weighting, attached to backend services.
-
Policy (Policy layer): Defines configurations such as circuit breaking, rate limiting, and JWT authentication. Can attach to a gateway, route, or backend service.
Gateway API solutions in ACK
Choose a Gateway API solution based on your business needs:
|
Solution |
Gateway with Inference Extension |
ALB (Application Load Balancer) |
|
Overview |
Gateway with Inference Extension is built on open source Envoy Gateway, optimized for cloud-native and AI inference scenarios. Listens for Gateway API resources to dynamically manage gateways and north-south traffic. Not fully managed—deployed on cluster nodes, requires O&M, and has no cloud product SLA. |
ALB Ingress Controller supports the Gateway API from v2.17.0. Configure resources such as Gateway and HTTPRoute to route external traffic to in-cluster workloads. The controller converts Gateway API changes into ALB listener rules, routing rules, and server group configurations in real time. |
|
Scenarios |
General traffic and AI inference scenarios |
General traffic scenarios |
|
Core advantages |
|
|
|
References |