gateway-api
gateway-api copied to clipboard
kubernetes-sigs
Repository for the next iteration of composite service (e.g. Ingress) and load balancing APIs.
**What would you like to be added**: The ability for a HTTPS (or TLS generally) endpoint to require that the client present a certificate that can be validated according to...
There are multiple cases where it may make sense to not require a gateway owner to specify a listener port: 1. Where a port number is irrelevant or nonsensical -...
**What type of PR is this?** /kind documentation **What this PR does / why we need it**: The KubeVela community focuses on the practice of application specification, and we agree...
**What would you like to be added**: - Add [`ListenerConditionType`](https://gateway-api.sigs.k8s.io/v1alpha2/references/spec/#gateway.networking.k8s.io%2fv1alpha2.ListenerConditionType) `Attached` (or possibly `Accepted` for parity with other objects, ref #1111 ), deprecate `Detached` **Why this is needed**: From a...
**What would you like to be added**: An option for defining a list of IP ranges that should be allowed/denied to call a certain HTTPRoute **Why this is needed**: When...
**Overview** The current implementation of the Gateway API appears to be based on a network proxy model as its core networking construct. This use case/issue makes the case to broaden...
See also: https://github.com/kubernetes/ingress-nginx/issues/6011 **What would you like to be added**: I would like to be able to have rate limiting (throttling) as part of the standard way of defining an...
Currently CertificateAuthorityRef is optional and can refer to an object like secret. The spec does not define what happens when this is not set - is this essentially `-k`/`InsecureSkipVerify` or...
There has always been the goal of using Gateway to fill the role that is currently filled by Services of type LoadBalancer (i.e. a single-purpose layer 4 proxy that sends...
This issue is closely related to #204. There should be a way for applications to indicate that they want WebSocket streams for [HTTP/1.1](https://tools.ietf.org/html/rfc8441) or [HTTP/2](https://tools.ietf.org/html/rfc6455). One way to do this...
Metadata
Owner
Metadata
Repository for the next iteration of composite service (e.g. Ingress) and load balancing APIs.