gateway-api
gateway-api copied to clipboard
Repository for the next iteration of composite service (e.g. Ingress) and load balancing APIs.
**What would you like to be added**: A test to ensure implementations can handle multiple Gateways in a route status. **Why this is needed**: This is a shared status field,...
/kind documentation **What this PR does / why we need it**: Updated documentation page regarding BackendTLSPolicy with the following fields: - Gateway backendTLS field - subjectAltNames field - options field...
**What type of PR is this?** /kind documentation **What this PR does / why we need it**: Moves the Glossary to the GAMMA section to avoid misunderstanding and facilitate clear...
**What would you like to be added**: BackendTLS should have the ability to be defined in more robust ways than just attached to a Service by the application developer **Why...
**What would you like to be added**: GRPCRoute coverage in http-request-mirror tests **Why this is needed**: cause.. why not? :) This is to improve coverage for GRPCRoute conformance tests. We...
[GEP-1767](https://gateway-api.sigs.k8s.io/geps/gep-1767/) cites https://fetch.spec.whatwg.org/#cors-safelisted-method saying that CORS-safelisted methods are `GET`, `HEAD`, and `POST` (this is consistent with the Mozilla [documentation](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Access-Control-Allow-Methods)). According to the GEP, these "are always allowed, regardless of whether...
This is a followup to a surprisingly long thread on [slack](https://kubernetes.slack.com/archives/CR0H13KGA/p1738253555742969). Our spec has a very [detailed table](https://github.com/kubernetes-sigs/gateway-api/blob/5dd3155c9069144bc7c79e413ac92ac4dae14251/apis/v1/httproute_types.go#L1105-L1119) of expectations for `ReplacePrefixMatch` field. However it does not cover the case...
When updating [gateway-api-rs](https://github.com/kube-rs/gateway-api-rs) to Gateway API `v1.3.0`, the generators failed for the experimental version of `HTTPRoute` due to a boolean enum in the spec that was introduced for CORS. ```yaml...
GEP-1767 confuses HTTPCORSFilter.AllowCredentials being set with HTTP request containing credentials
There are multiple places [[1](https://github.com/kubernetes-sigs/gateway-api/blob/1a9fdd310de40f83c5ad58c1215d1c6c2c6832cb/geps/gep-1767/index.md?plain=1#L224-L241)], [[2](https://github.com/kubernetes-sigs/gateway-api/blob/1a9fdd310de40f83c5ad58c1215d1c6c2c6832cb/geps/gep-1767/index.md?plain=1#L319-L340)], [[3](https://github.com/kubernetes-sigs/gateway-api/blob/1a9fdd310de40f83c5ad58c1215d1c6c2c6832cb/geps/gep-1767/index.md?plain=1#L387-L408)], [[4](https://github.com/kubernetes-sigs/gateway-api/blob/1a9fdd310de40f83c5ad58c1215d1c6c2c6832cb/geps/gep-1767/index.md?plain=1#L457-L459)] in GEP-1767 saying that a certain response header cannot contain the wildcard (`*`) if the Gateway API `HTTPCORSFilter.AllowCredentials` field is set, e.g.:...
**What type of PR is this?** /kind cleanup **What this PR does / why we need it**: This PR updates golangci-lint to v2 to keep the linters and linting tool...