fa372e4b93This change adds conformance test for TLSRoute when it has mixed tls modes on the same port. When an implementation claims to support two listeners, both on the same port, both of type TLS but one having its mode as Passthrough and the other as Terminate, it must route the traffic correctly, and in case of a Terminated listener, terminate the TLS on proxy and send unencrypted to the backend. Otherwise, in case it does not support Mixed TLS modes, it must report on its listener a failure to set these 2 listeners. |
||
|---|---|---|
| .github | ||
| .openvex/templates | ||
| apis | ||
| apisx | ||
| applyconfiguration | ||
| CHANGELOG | ||
| config/crd | ||
| conformance | ||
| docker | ||
| docs | ||
| examples | ||
| geps | ||
| gwctl | ||
| hack | ||
| pkg | ||
| roles | ||
| site-src | ||
| tests | ||
| tools | ||
| .custom-gcl.yml | ||
| .gitattributes | ||
| .gitignore | ||
| .golangci-kal.yml | ||
| .golangci.yml | ||
| .yamllint.yaml | ||
| CHANGELOG.md | ||
| cloudbuild.yaml | ||
| code-of-conduct.md | ||
| CONTRIBUTING.md | ||
| crd-ref-docs.yaml | ||
| go.mod | ||
| go.sum | ||
| go.work | ||
| LICENSE | ||
| Makefile | ||
| mkdocs.yml | ||
| nav.yml | ||
| 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.4.1 release of this project.
This version of the API has GA level support for the following resources:
v1.GatewayClassv1.Gatewayv1.HTTPRoutev1.GRPCRoutev1.BackendTLSPolicy
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.