Free tools Windows power users keep installed
One-click scans. No signup required.
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
NGINX Gateway Fabric connects Kubernetes Gateway API resources to NGINX data planes: attach a Gateway to the fabric’s GatewayClass, and the controller creates an NGINX deployment and Service in the Gateway’s namespace. Before installing, verify the supported Kubernetes and Gateway API versions, decide how the Service will be reachable, and separate the quick-start example from production setup.
What NGINX Gateway Fabric does
F5 describes NGINX Gateway Fabric as “a Kubernetes Gateway API implementation which uses NGINX as the data plane.” The controller watches Gateway API resources and turns applicable configuration into deployed NGINX resources. F5’s Gateway architecture documentation explains this relationship.
A Gateway associated with the fabric’s GatewayClass causes an NGINX deployment and a Service to be created in the Gateway’s namespace. A separate Gateway can provision a separate data plane, which can provide distinct traffic entry points or help organize isolation boundaries. This does not, by itself, guarantee that clients outside the cluster can reach the Gateway: the Service type and the cluster’s networking determine reachability.
Check compatibility before installing
Version compatibility changes over time. The F5 technical specifications page lists NGINX Gateway Fabric 2.7.2 with Gateway API 1.6.1 and Kubernetes 1.32 or later; its table lists NGINX Open Source 1.31.6 for that release. Treat these as the versions in the cited compatibility snapshot, not permanent requirements, and check the current technical specifications before choosing versions.
#1 Best Overall
Install the standard Gateway API CRDs at a version supported by the fabric before installing NGINX Gateway Fabric. The Helm installation guide specifies Helm 3.0 or later and documents installation paths for NGINX Open Source and NGINX Plus. The Plus path has additional setup. Choose between them based on your licensing or subscription requirements and the features your deployment needs; the documentation does not establish a universal winner.
Choose how Gateway traffic will reach the cluster
The Helm guide documents LoadBalancer as the default Service type for a Gateway and NodePort as an alternative. Select based on what your cluster’s service implementation supports, how clients reach the cluster, and how your team operates network exposure.
Rank #2
| Service type | What to check |
|---|---|
LoadBalancer (chart default) |
Confirm the cluster or its infrastructure provides a working LoadBalancer service implementation and that the resulting address is reachable by intended clients. See the F5 Helm guide. |
NodePort (available alternative) |
Confirm that clients can reach the relevant nodes and node ports, and that your network and operational model support that exposure. See the F5 Helm guide. |
Install and configure it in the right order
- Check the compatibility matrix. Choose a supported combination of Kubernetes, Gateway API, and NGINX Gateway Fabric versions using the technical specifications.
- Install standard Gateway API resources. Apply the CRDs for the supported Gateway API version before installing the fabric, as required by the Helm guide.
- Install NGINX Gateway Fabric. Follow the Helm guide for the NGINX Open Source or NGINX Plus path you selected. For production, configure secure authentication certificates as appropriate to your environment.
- Define a Gateway and routes. Create a Gateway using the fabric’s GatewayClass, configure its listener, and attach HTTPRoute resources for the application paths you want to serve. Verify the created deployment and Service, then test reachability through the selected Service exposure and your cluster network.
Use the quick start for evaluation, not production
F5’s Get started guide demonstrates the flow with a local kind cluster: install Gateway API resources, install the Helm chart, create a Gateway with an HTTP listener, and attach HTTPRoute resources. Its example lists Docker, kubectl, Helm, Go, and curl as tools for that setup. F5 explicitly says, “This document is for trying out NGINX Gateway Fabric, and not intended for a production environment.” Use the production installation documentation and secure configuration guidance for a live deployment.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsReview telemetry and optional API extensions
According to F5’s product telemetry documentation, telemetry is enabled by default, sent once every 24 hours to an F5-managed service over HTTPS, and can be disabled during installation. F5 says the telemetry does not collect personally identifiable information. Check the documented opt-out and your organization’s privacy policy during deployment review.
The API reference lists extension resources including AuthenticationFilter, RateLimitPolicy, UpstreamSettingsPolicy, WAFPolicy, and ObservabilityPolicy. Their presence in the API reference does not mean a feature is enabled or suitable in every installation. Consult the documentation for the specific resource and its version compatibility before relying on it. See the API reference.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
