nginx-gateway-fabric
nginx-gateway-fabric copied to clipboard
nginxinc
NGINX Gateway Fabric provides an implementation for the Gateway API using NGINX as the data plane.
**As a** user of NGF utilizing TLS passthrough **I want** to enable my TLSRoute to route to a service in another namespace **So that** my single Gateway object can route...
As an NGF user, I want to know what type of data plane fields I can configure, So that I know how to change the settings of my data plane...
Instructions on how to get N+ images are split across two docs: - https://docs.nginx.com/nginx-gateway-fabric/installation/ngf-images/jwt-token-docker-secret/ - https://docs.nginx.com/nginx-gateway-fabric/installation/ngf-images/pulling-ngf-image/ which makes it hard to follow. Additionally, the "Pushing an NGINX Plus image to...
We want to be able to catch problems with the `values.yaml` files early rather than running into errors once NGF is deployed. Add a schema to enforce parameters/types for the...
We currently have a document for modifying response headers: https://docs.nginx.com/nginx-gateway-fabric/how-to/traffic-management/response-headers/ We should enhance this doc to also include information about configuring request headers.
Add support for [TlsRouteRule.BackendRef.Weight](https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1alpha2.TLSRouteRule) which would allow users to configure traffic splitting for TLSRoutes. Notes: - this is an extended feature - TLSRoute has undefined behavior when multiple TLSRouteRules are...
**Describe the bug** When using NGINX Plus with NGINX Gateway Fabric, the upstreams are applied correctly when HTTPRoute is applied via the API, but when the deployment is scaled, upstreams...
When scale test runs with NGINX Plus with 648 upstream servers, it reports both NGF and NGINX Plus errors, because at some point the upstream zone size is no longer...
NGF currently does not emit any *_server_zone_* metrics from NGINX Plus. This appears to be an oversight in our exposure of metrics, so this is something we need to fix....
As a NGF user with a large Kubernetes Cluster I want to separate my traffic using multiple NGF Gateways So that I can have separate pieces of infrastructure manage different...