The official NGINX Gateway Fabric (NGF) demo shows how to run a local Kubernetes Gateway API implementation, deploy a sample application, and test traffic routing through NGINX. It uses kind and Helm and is intended for evaluation—not production. NGF is an open-source Gateway API implementation with NGINX as its data plane.
What the NGF demo shows
The quickstart creates a local Kubernetes cluster with kind, installs the Gateway API custom resource definitions (CRDs), installs NGF, deploys an example application, and tests access to it. It is a practical way to see how a Gateway API configuration reaches an NGINX data plane; a single sample route does not establish production readiness or performance.
As an Amazon Associate I earn from qualifying purchases.
The official guide says: “This document is for trying out NGINX Gateway Fabric, and not intended for a production environment.” Follow the official getting-started guide for the current commands, and use the separate deployment documentation for production planning.
How NGF fits into Kubernetes
NGF separates its control plane from its NGINX data plane. The control plane watches Gateway API and related Kubernetes resources, translates configuration, and manages the NGINX data plane. When a Gateway attaches to an NGF-managed GatewayClass, NGF provisions a Service and an NGINX deployment; multiple Gateways can result in separate data-plane deployments.
The project describes use cases including HTTP and TCP/UDP load balancing, reverse proxying, and API gateway behavior for applications running on Kubernetes. The demo illustrates the configuration flow with an example; it is not a load test or a measure of production capacity. See the NGF documentation for the project’s architecture and deployment details.
Prerequisites
The official quickstart lists these requirements:
- Go 1.16 or newer, used by kind
- Docker
- kind
- kubectl
- Helm 3.0 or newer
- curl
You also need a machine able to run Docker and a local Kubernetes cluster. Check the live guide before starting: its CRD release, chart values, and commands can change.
Run the official local demo
Use the guide’s commands rather than copying an old command sequence: the exact values and compatible releases are version-sensitive. The workflow is:
Recommended Free Tools
- Create the kind cluster. The guide configures host port mappings so you can reach the example from the host machine.
- Install Gateway API CRDs. These define the Gateway API resources that NGF will watch. Use the CRD version specified by the guide for the NGF release you chose.
- Install NGF with Helm. The quickstart uses a Helm chart and NodePort configuration to expose the data plane for local testing.
- Deploy the sample application and route. Apply the example resources from the guide so the Gateway can direct requests to the application.
- Test access with curl. Send a request to the host-mapped endpoint and confirm the sample application responds. If it does not, check that the cluster, NGF resources, Gateway, route, and application are ready and that you are using the endpoint and port specified in the current guide.
Check compatibility before choosing a release
NGF, Gateway API, and Kubernetes versions must be compatible. The F5 technical specifications page listed this combination in its current version row, accessed September 28, 2026:
| NGF release | Gateway API | Kubernetes |
|---|---|---|
| 2.7.2 | 1.6.1 | 1.32 or newer |
This is a compatibility snapshot, not a performance figure. Other NGF releases have different combinations; consult the technical specifications matrix when selecting a release. Compare the Gateway API release, minimum Kubernetes version, supported NGINX OSS or Plus version, and any optional integrations you plan to use.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.NGINX Plus and production considerations
NGINX Plus is an optional commercial data-plane choice, not a prerequisite for the basic local demo. Its use involves additional setup and credential handling; follow the current NGF documentation for the applicable instructions.
For production, treat the quickstart only as an orientation. Review the production deployment guidance for your environment, including configuration, secrets and authentication handling, supported versions, and operational requirements. A successful local curl request confirms only that the sample path works in that demo setup.
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.
