Kubernetes Gateway API

Kubernetes Gateway API is an evolution of the Ingress API that provides more flexibility, expressiveness, and extensibility for managing service traffic within Kubernetes clusters.

Key Features

1. Role-Based Model: Unlike Ingress, Gateway API introduces clear separation of concerns by defining different roles such as GatewayClass, Gateway, HTTPRoute, and TCPRoute.

2. Multiple Listeners: Gateways can support multiple listeners on different ports and protocols.

3. Cross-Namespace Routing: Allows defining routing policies across different namespaces, improving multi-tenant support.

4. Service Mesh Integration: Can be used alongside service meshes for advanced traffic control.

5. More Extensible than Ingress: Supports different route types, making it adaptable for various protocols beyond just HTTP.

Core API Resources

1. GatewayClass: Defines a high-level abstraction for load balancers and network configurations.

2. Gateway: Represents an instance of a GatewayClass, defining how traffic should be handled.

3. HTTPRoute: Specifies routing rules for HTTP traffic.

4. TCPRoute, UDPRoute, GRPCRoute: Define routing for non-HTTP protocols.

5. ReferenceGrant: Allows controlled cross-namespace resource references.


Links: https://kubernetes.io/docs/concepts/services-networking/gateway/


I really love Gateway API more than Ingress. Please try it out; it will make your life easier.


If you have any configuration issues with it feel free to reach out to me.

#backend #Kubernetes