The Kubernetes Gateway API is a specification and implementation framework developed under the Kubernetes SIG Network working group, serving as the next iteration of composite service and load balancing APIs beyond the traditional Ingress model. The repository contains the formal specification and Custom Resource Definitions that define how traffic routing and gateway management should work within Kubernetes clusters. The project reached general availability status with the v1 release in version 1.6.0, establishing a stable foundation for production use.
The Gateway API introduces several core resource types that have achieved GA-level support, including GatewayClass, Gateway, HTTPRoute, GRPCRoute, TLSRoute, TCPRoute, UDPRoute, BackendTLSPolicy, and ReferenceGrant. These resources work together to provide flexible, role-oriented traffic management capabilities that separate concerns between infrastructure operators who manage gateways and application developers who define routing rules. The API supports multiple transport protocols and security models, enabling use cases ranging from simple HTTP routing to complex multi-protocol load balancing scenarios.
The repository's scope extends across multiple domains including service mesh integration, software-defined networking, HTTP and HTTPS routing, traffic management, and multi-cluster networking scenarios.
Documentation and community engagement are central to the project's approach. The specification is published on the official project website at gateway-api.sigs.k8s.io, with comprehensive guides covering API concepts, security models, and getting started instructions. The project maintains a conformance testing framework that allows implementations to validate their compliance with the specification and submit conformance reports, creating a standardized way for users to understand which features different Gateway API implementations support.
The repository is written primarily in Go and serves as the authoritative source for the Gateway API specification within the Kubernetes ecosystem. Community participation occurs through regular meetings, developer guides, and the dedicated Kubernetes Slack channel for SIG Network Gateway API discussions. The project operates under the Kubernetes Code of Conduct, establishing clear expectations for community participation and collaboration.
