awesome-repositories.com
Blog
MCP
awesome-repositories.com

Discover the best open-source repositories with AI-powered search.

ExploreCurated searchesOpen-source alternativesSelf-hosted softwareBlogSitemap
ProjectMCP serverAboutHow we rankPress
LegalPrivacyTerms
© 2026 Bringes Technology SRL·VAT RO45896025·hello@awesome-repositories.com
kubernetes-sigs avatar

kubernetes-sigs/gateway-api

0
View on GitHub↗

Gateway Api

The Gateway API is a standardized set of resources for routing HTTP, gRPC, and TCP traffic into and within Kubernetes clusters. It serves as a framework for defining load balancer listeners and routing rules for both Layer 4 and Layer 7 protocols, acting as a specification for ingress and service mesh traffic interfaces.

The project utilizes a role-oriented configuration that separates infrastructure provisioning from routing logic. It implements a class-based provider selection system to match requested infrastructure to specific controller implementations and employs a conformance-driven specification to ensure all implementations pass standardized tests.

The API covers a broad range of networking domains, including external ingress management, internal service mesh routing, and Layer 4 load balancing. It incorporates security and access control primitives such as backend TLS configuration, hostname ownership delegation to prevent route hijacking, and cross-namespace reference authorization.

The project includes a networking conformance suite used to verify that implementations adhere to the official API specifications.

AI search

Explore more awesome repositories

Describe what you need in plain English — the AI ranks thousands of curated open-source projects by relevance.

Start searching with AI
gateway-api.sigs.k8s.io
↗

Features

  • Ingress Controllers - Provides a standardized API for routing external web traffic into Kubernetes clusters using role-oriented configuration.
  • Ingress Controllers - Provides a standardized API to define entry points and route external HTTP, gRPC, and TCP traffic into Kubernetes clusters.
  • Service Mesh - Manages internal traffic flow between services within a cluster using routing rules associated with service resources.
  • Hostname Ownership Delegation - Prevents route hijacking by assigning specific hostnames to dedicated namespaces on gateway listeners.
  • Kubernetes Ingress Specifications - Implements a role-oriented API that separates infrastructure provisioning from traffic routing for cluster entry points.
  • Mesh Traffic Policy Management - Defines routing rules and policies for managing communication between internal services within a cluster.
  • Kubernetes Gateway API Standard - Provides the standardized set of resources for routing HTTP, gRPC, and TCP traffic in Kubernetes.
  • Layer 4 and Layer 7 Proxies - Provides a framework for defining load balancer listeners and routing rules for both Layer 4 and Layer 7 protocols.
  • Load Balancers - Triggers the automated provisioning of load balancer instances and network addresses based on requested infrastructure classes.
  • L4 and L7 Routing Abstractions - Abstracts traffic management into distinct layers for L4 TCP/UDP and L7 HTTP/gRPC routing.
  • Traffic Routing - Implements a standardized set of resources for directing HTTP and gRPC traffic to internal services.
  • Layer 4 TCP Routing - Directs TCP, UDP, and TLS traffic to expose non-HTTP services through standardized gateway implementations.
  • Route Binding Permissions - Implements selector-based controls to define which namespaces are authorized to attach routing rules to a gateway listener.
  • Role-Oriented Resource Separation - Separates infrastructure provisioning from routing logic by dividing configuration into gateway, route, and backend resources.
  • Protocol Conformance Testing - Verifies that networking implementations adhere to official specifications via a standardized test suite.
  • Protocol Conformance Suites - Provides a standardized test suite to ensure networking implementations adhere to the official API specifications.
  • Specification Conformance Validation - Defines a rigid set of resource schemas and behaviors verified through standardized conformance tests.
  • Controller Class Selection - Provides a class-based system to match requested infrastructure to specific controller implementations.
  • Selector-Based Rule Filtering - Uses label selectors to bind routing rules to gateway listeners and manage namespace influence.
  • gRPC Traffic Routing - Directs requests to gRPC services using protocol-specific routing rules to optimize high-performance API communication.
  • Hostname Delegation - Assigns hostnames and namespaces to specific gateway listeners to prevent route hijacking.
  • Cross-Namespace Reference Grants - Uses explicit permission objects to allow routing resources in one namespace to target services in another.
  • TLS Traffic Encryption - Defines how gateways communicate with backend services using TLS to secure traffic between the proxy and application.
  • Namespace Access Controls - Grants permission for resources in one namespace to reference objects in another to link services and routes.
2,661 stars·668 forks·Go·apache-2.0·28 views

Star history

Star history chart for kubernetes-sigs/gateway-apiStar history chart for kubernetes-sigs/gateway-api

How this analysis was created: This summary and feature list are AI-generated from collected project material and can contain mistakes. Stars, license and language are imported from GitHub. Inclusion does not mean that we have tested or audited this project. Check the source documentation for any feature you depend on. Learn more on our About page.

Projects sharing features with Gateway Api

These projects share indexed features with Gateway Api. Shared tags can include platform or build tooling; verify the primary use case before treating a result as a replacement.
  • alibaba/higressalibaba avatar

    alibaba/higress

    7,558View on GitHub↗

    Higress is an AI API gateway and cloud-native traffic manager that functions as a Kubernetes ingress controller. It provides a centralized system for routing, securing, and optimizing traffic directed toward large language models, AI agents, and microservice architectures. The project distinguishes itself through deep AI orchestration, including the ability to host and manage Model Context Protocol servers that transform REST APIs into tools for AI agents. It features specialized AI infrastructure for model request proxying, protocol translation across multiple providers, and semantic-based c

    Goai-gatewayai-nativeapi-gateway
    View on GitHub↗7,558
  • weaveworks/flaggerweaveworks avatar

    weaveworks/flagger

    5,362View on GitHub↗

    Flagger is a Kubernetes operator designed to automate the lifecycle of application deployments through progressive delivery. It functions as a controller that monitors custom resource definitions to orchestrate complex release strategies, including canary, blue/green, and A/B testing. By continuously reconciling the desired cluster state with the actual environment, it ensures that deployments adhere to defined specifications while managing the underlying infrastructure required for traffic routing. The project distinguishes itself through a sophisticated metric-driven analysis loop that eval

    Go
    View on GitHub↗5,362
  • linkerd/linkerdlinkerd avatar

    linkerd/linkerd

    5,316View on GitHub↗

    Linkerd is a Kubernetes service mesh that manages network traffic between microservices. It functions as a transparent networking proxy, layer 7 traffic manager, and mutual TLS security layer, providing observability and reliability for service-to-service communication without requiring changes to application code. The project distinguishes itself through a sidecar-proxy architecture that intercepts TCP and application-level traffic to provide automatic mutual TLS encryption and identity verification. It enables cross-cluster service networking to link multiple clusters and implements cloud-n

    Scalacloud-nativelinkerdservice-discovery
    View on GitHub↗5,316
  • kubernetes/ingress-nginxkubernetes avatar

    kubernetes/ingress-nginx

    19,492View on GitHub↗

    This project is a Kubernetes Ingress Controller that functions as a layer 7 traffic router and NGINX reverse proxy. It serves as a secure network gateway, directing external HTTP and HTTPS traffic to backend services within a cluster based on declarative routing rules. The controller acts as a TLS termination gateway to secure traffic and integrates with Prometheus to expose request metrics and latency data for cluster monitoring. It supports canary deployment workflows by implementing weight-based traffic splitting between different versions of a service. The system manages external access

    Goingress-controllerkubernetesnginx
    View on GitHub↗19,492
Compare all 30 related projects→

Curated searches featuring Gateway Api

Hand-picked collections where Gateway Api appears.
  • APIs

Frequently asked questions

What does kubernetes-sigs/gateway-api do?

The Gateway API is a standardized set of resources for routing HTTP, gRPC, and TCP traffic into and within Kubernetes clusters. It serves as a framework for defining load balancer listeners and routing rules for both Layer 4 and Layer 7 protocols, acting as a specification for ingress and service mesh traffic interfaces.

What are the main features of kubernetes-sigs/gateway-api?

The main features of kubernetes-sigs/gateway-api are: Ingress Controllers, Service Mesh, Hostname Ownership Delegation, Kubernetes Ingress Specifications, Mesh Traffic Policy Management, Kubernetes Gateway API Standard, Layer 4 and Layer 7 Proxies, Load Balancers.

Which projects share features with kubernetes-sigs/gateway-api?

Projects with overlapping indexed features include: alibaba/higress — Higress is an AI API gateway and cloud-native traffic manager that functions as a Kubernetes ingress controller. It… weaveworks/flagger — Flagger is a Kubernetes operator designed to automate the lifecycle of application deployments through progressive… linkerd/linkerd — Linkerd is a Kubernetes service mesh that manages network traffic between microservices. It functions as a transparent… kubernetes/ingress-nginx — This project is a Kubernetes Ingress Controller that functions as a layer 7 traffic router and NGINX reverse proxy. It… bunkerity/bunkerweb — BunkerWeb is a containerized suite of infrastructure tools that functions as a cloud-native web application firewall… jcmoraisjr/haproxy-ingress — This project is a Kubernetes ingress controller that manages external traffic by dynamically configuring the HAProxy…