Benefits of Gateway API

Benefits of Gateway API A workflow diagram generated by Archify. 01 / Gateway API Features Expressiveness · Multiple protocol support · Gateway API Features · HTTP · gRPC · TCP · UDP Expressiveness Multiple protocol support HTTP · gRPC · TCP · UDP Role Separation · Role-based permissions · Gateway API Features · infra · operator · developer Role Separation Role-based permissions infra · operator · developer Portability · Standardized resources · Gateway API Features · no annotation dependence Portability Standardized resources no annotation dependence Extensibility · CRD-based extension · Gateway API Features Extensibility CRD-based extension Legend Extension mechanism Permission model Protocol routing Standard resources

Ingress API Limitations Addressed

  • • Limited expressiveness: poor support for TCP/UDP/gRPC beyond HTTP routing
  • • No role separation: hard to separate infrastructure admin and application developer permissions
  • • Annotation abuse: implementation-specific features handled via annotations, reducing portability
  • • Limited extensibility: difficult to add new protocols or features

Development and Implementations

  • • Next-generation ingress API developed by SIG-Network
  • • Supported by implementations such as Istio, Cilium, and Envoy Gateway