Use Manifests to install experimental NGINX Gateway Fabric versions

This page describes how to use Manifests to install experimental NGINX Gateway Fabric versions.

The deployment process is similar to other installation procedures, and can be done with NGINX Open Source or NGINX Plus.

Using experimental NGINX Gateway Fabric versions can allow you to test API resources from upcoming releases as outlined by the Milestone Roadmap.

For information on API resource support, view the Gateway API compatibility topic.

The main requirement for installing experimental NGINX Gateway Fabric versions is to change the URL for each resource during the installation steps.

Each of the following sections provides the necessary replacement URL and any other necessary information.

API resources

The Gateway API resources from the experimental channel include everything in the standard release channel.

To install API resources from the experimental channel, run the following command:

kubectl kustomize "https://github.com/nginx/nginx-gateway-fabric/config/crd/gateway-api/experimental?ref=v2.2.2" | kubectl apply -f -

Custom resource definitions

The custom resource definitions (CRDs) for an experimental NGINX Gateway Fabric release are the same as a regular deployment, and do not require replacement.

NGINX Gateway Fabric deployment

Warning

To install an experimental NGINX Gateway Fabric version, you must also install experimental API resources. They cannot be mis-matched.

To deploy an experimental NGINX Gateway Fabric instance, use the command based on your NGINX type:

kubectl apply -f https://raw.githubusercontent.com/nginx/nginx-gateway-fabric/v2.2.2/deploy/experimental/deploy.yaml

kubectl apply -f https://raw.githubusercontent.com/nginx/nginx-gateway-fabric/v2.2.2/deploy/nginx-plus-experimental/deploy.yaml