8ecfe98081* Remove implementation-specific methods/headers
Previously, the GEP mentioned allowing "implementatio-specific default
methods and headers". It's not obvious what that means, but my
understanding is that this would allow implementations to arbitrarily
add certain values (not specified by the user) to the headers
Access-Control-Allow-Methods and Access-Control-Request-Headers`.
It does not seem to be needed. We can revisit this aspect
if it turns out otherwise.
Signed-off-by: Damian Sawicki <dsawicki@google.com>
* Unify gep-1767 and httproute_types.go
It seems that not all changes in GEP 1767 were correctly reflected in
apis/v1/httproute_types.go. This is now fixed.
Signed-off-by: Damian Sawicki <dsawicki@google.com>
* Allow specific Allow-Origin despite wildcard
As per
https://github.com/kubernetes-sigs/gateway-api/pull/4494#discussion_r2770157900
Mozilla has an example where in response to an uncredentialed request,
the server responds with `Access-Control-Allow-Origin: *`.
However, responding with the value of the Origin from the request is
also valid (and the only allowed behavior for credentialed requests),
and it is the behavior of some implementations as per
|
||
|---|---|---|
| .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.