- Go 91.8%
- Python 2.5%
- Shell 2.4%
- HTML 2.2%
- Makefile 0.4%
- Other 0.6%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
ddbd6bafd2* GEP-1619: Backend as attachment point for session persistence Move session persistence from BackendTrafficPolicy and route-inline to the Backend resource (GEP-4488). Remove BTP and route-inline API sections, update API Attachment Points to only Backend, and deprecate route-inline. * GEP-1619: Traffic Split applies AFTER Backend Selection Prior ART shows that most, if not all, implementations and data planes apply session persistence after routing (backend selection). Update traffic splitting guidance so that session persistence does not override backend selection. Also remove redundant mixed-backends edge case. * GEP-1619: Code Review Updates - Move SessionPersistence to be within EndpointSelector in Backend - Specify relationship with backend protocol - Clarify that the cookie/header MAY not be sent to the backend * GEP-1619: Backend SHOULD receive Cookie Update from MAY to SHOULD for whether the backend behavior of receiving the gateway generated cookie based on prior art. |
||
| .github | ||
| .openvex/templates | ||
| api/openapi-spec | ||
| apis | ||
| apisx | ||
| applyconfiguration | ||
| CHANGELOG | ||
| config/crd | ||
| conformance | ||
| examples | ||
| geps | ||
| gwctl | ||
| hack | ||
| pkg | ||
| roles | ||
| site | ||
| tests | ||
| tools | ||
| wasm | ||
| .custom-gcl.yml | ||
| .gitattributes | ||
| .gitignore | ||
| .golangci-kal.yml | ||
| .golangci.yml | ||
| .yamllint.yaml | ||
| AI-POLICY.md | ||
| CHANGELOG.md | ||
| code-of-conduct.md | ||
| CONTRIBUTING.md | ||
| crd-ref-docs.yaml | ||
| crdify.yaml | ||
| go.mod | ||
| go.sum | ||
| go.work | ||
| LICENSE | ||
| Makefile | ||
| netlify.toml | ||
| OWNERS | ||
| OWNERS_ALIASES | ||
| README.md | ||
| RELEASE.md | ||
| RELEASE_MANAGEMENT.md | ||
| SECURITY_CONTACTS | ||
Kubernetes Gateway API
The Gateway API is a part of SIG Network, and this repository contains the specification and Custom Resource Definitions (CRDs).
Status
The latest supported version is v1 as released by
the v1.6.1 release of this project.
This version of the API has GA level support for the following resources:
v1.GatewayClassv1.Gatewayv1.ListenerSetv1.HTTPRoutev1.GRPCRoutev1.TLSRoutev1.TCPRoutev1.UDPRoutev1.BackendTLSPolicyv1.ReferenceGrant
For all the other APIs and their support levels please consult the spec.
Documentation
Website
The API specification and detailed documentation is available on the project website: https://gateway-api.sigs.k8s.io.
Concepts
To get started, please read through API concepts and Security model. These documents give the necessary background to understand the API and the use-cases it targets.
Getting started
Once you have a good understanding of the API at a higher-level, check out getting started to install your first Gateway controller and try out one of the guides.
References
For a complete API reference, please refer to:
Gateway API conformance
If you are developing a Gateway API implementation and want to run conformance tests against your project and eventually submit the proof of conformance, visit the conformance documentation for the test suite documentation, and the conformance reports readme to see the reports submission rules. If you are a user who wants to explore the features supported by the various implementations, navigate the conformance reports
Contributing
Community meeting schedule, notes and developer guide can be found on the community page. Our Kubernetes Slack channel is #sig-network-gateway-api.
Code of conduct
Participation in the Kubernetes community is governed by the Kubernetes Code of Conduct.