# kubernetes-sigs/gateway-api

Repository for the next iteration of composite service (e.g. Ingress) and load balancing APIs.

Repository: https://github.com/kubernetes-sigs/gateway-api
Canonical: https://ross.abutalabs.com/products/gateway-api
Homepage: https://gateway-api.sigs.k8s.io
Language: Go
License: Apache-2.0
License Family: permissive
Topics: k8s-sig-network, kubernetes, gateway-api, sig-network, networking
Last push: 2026-08-26T20:15:53+00:00

## Health v2 (maintenance only)
Score: 93/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 99, release rhythm 81, longevity 100
- inputs: {"age_days": 2497, "days_push": 7, "days_rel": 48, "gap_med": 58, "n_releases_24m": 10}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 2978, forks 779 (observed 2026-08-28T04:07:33.006280+00:00)

## What it is
Kubernetes Gateway API is the official successor to Ingress, providing a role-oriented, expressive specification and CRDs for L4/L7 routing, load balancing, and service mesh traffic management. This repository contains the API specification, Custom Resource Definitions, and a conformance test suite for implementations.

## Use cases
- replace ingress with gateway api
- route http traffic into a kubernetes cluster
- configure grpc routing in kubernetes
- manage tls routes and gateway listeners
- standardize load balancing apis across gateway controllers
- east-west service mesh traffic routing
- verify gateway controller conformance

## When to choose
- you need role-oriented ingress/load-balancing config in Kubernetes
- you want portable routing APIs across multiple gateway controllers
- you need HTTP, GRPC, TLS, TCP, or UDP routing with a stable GA API
- you are building or validating a Gateway API controller implementation

## When to avoid
- you need a concrete traffic proxy rather than an API spec (pick a controller like Envoy Gateway or Istio)
- you run a very old Kubernetes cluster without CRD support for the required version
- you only need simple host/path ingress and prefer minimal tooling

## Facets
- artifact type: framework
- maturity: stable
- function: routing, api-framework, middleware, networking
- domain: networking, infrastructure-as-code, cloud-computing, apis
- platform: go, cloud, self-hosted
- tags: gateway-api, ingress, load-balancing, crds, service-mesh, k8s-sig-network, l7-routing, l4-routing, kubernetes

## Member repositories
- kubernetes-sigs/gateway-api (main) score 93

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:07:33.006280+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T07:31:31.826690+00:00, confidence not recorded.
  - readme: https://github.com/kubernetes-sigs/gateway-api (fetched 2026-08-28T04:07:33.006280+00:00, sha 1dd96bbd2e77)
  - homepage: https://gateway-api.sigs.k8s.io (fetched 2026-08-29T09:46:39.707281+00:00, sha 1bde00cd495a)
  - site_page: https://gateway-api.sigs.k8s.io/docs (fetched 2026-08-29T09:46:39.709624+00:00, sha 11d71ec4b9d0)
- Data as of 2026-08-30T08:39:29.467469+00:00.