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.
**Describe the bug** When `autoscaling.enable: true` is configured in the Helm chart, the NGF controller updates the deployment and modifies the `spec.replicas` field in conflict with the HPA. This causes...
NFR pipeline runs show errors in reconfig tests related to nginx.conf not being applied correctly consistently for two runs and need to be investigated Run 1 - https://github.com/nginx/nginx-gateway-fabric/pull/3991 Run 2...
With R34, NGINX Plus allows NGINX customers to send their license usage telemetry to F5 via an existing enterprise forward proxy in their environment. NGF should support these fields so...
Bug fixes and other changes that we want to backport into release branches can add a lot of dev cycles. Making this process easier will reduce friction when doing releases....
Both conformance and functional tests are failing inconsistently. We need an investigation into if there is a common root cause amongst failures. We see timeouts and many other types of...
In the nginx provisioner, we call [RegisterGateway](https://github.com/nginx/nginx-gateway-fabric/blob/main/internal/controller/provisioner/provisioner.go#L470) to create nginx resources upon initial gateway creation. However, with each of the objects initially created, a handler upsert event occurs and [updateOrDeleteResources](https://github.com/nginx/nginx-gateway-fabric/blob/main/internal/controller/provisioner/handler.go#L148)...
### Describe the bug The core issue lies in **`route_common.go`**: * Section name refs are expanded once during the build phase (`buildSectionNameRefs`) and then expanded again later when finding attachable...
**Describe the bug** NGF currently reads in every resource (Gateway, HTTPRoute, etc) in the system and stores in a map. It then filters the ones it cares about and builds...
For scale NFR tests, we currently only collect CPU and memory metrics for NGF pods. We should extend this to include NGINX pods as well, so we have full visibility...
As part of Gateway API release 1.4, the field `supportedFeatures` in GatewayClass spec is being moved to standard. The [story](https://github.com/kubernetes-sigs/gateway-api/issues/3164) tracking it on the Gateway API side.