Example

In this example we deploy NGINX Gateway Fabric, a simple web application, and then configure NGINX Gateway Fabric to route traffic to that application using HTTPRoute resources.

Running the Example

1. Deploy NGINX Gateway Fabric

Follow the installation instructions to deploy NGINX Gateway Fabric.

2. Deploy the Cafe Application

Create the coffee and the tea Deployments and Services:
```
kubectl apply -f cafe.yaml
```

Check that the Pods are running in the default Namespace:

kubectl -n default get pods

NAME                      READY   STATUS    RESTARTS   AGE
coffee-6f4b79b975-2sb28   1/1     Running   0          12s
tea-6fb46d899f-fm7zr      1/1     Running   0          12s

3. Configure Routing

Create the Gateway:
```
kubectl apply -f gateway.yaml
```
After creating the Gateway resource, NGINX Gateway Fabric will provision an NGINX Pod and Service fronting it to route traffic.

Save the public IP address and port of the NGINX Service into shell variables:
```
GW_IP=XXX.YYY.ZZZ.III
GW_PORT=<port number>
```
Create the HTTPRoute resources:
```
kubectl apply -f cafe-routes.yaml
```

4. Test the Application

To access the application, we will use curl to send requests to the coffee and tea Services.

To get coffee:

curl --resolve cafe.example.com:$GW_PORT:$GW_IP http://cafe.example.com:$GW_PORT/coffee

Server address: 10.12.0.18:80
Server name: coffee-7586895968-r26zn

To get tea:

curl --resolve cafe.example.com:$GW_PORT:$GW_IP http://cafe.example.com:$GW_PORT/tea

Server address: 10.12.0.19:80
Server name: tea-7cd44fcb4d-xfw2x

5. Using different hostnames

Traffic is allowed to cafe.example.com because the Gateway listener's hostname allows *.example.com. You can change an HTTPRoute's hostname to something that matches this wildcard and still pass traffic.

For example, run the following command to open your editor and change the HTTPRoute's hostname to foo.example.com.

kubectl -n default edit httproute tea

Once changed, update the curl command above for the tea service to use the new hostname. Traffic should still pass successfully.

Likewise, if you change the Gateway listener's hostname to something else, you can prevent the HTTPRoute's traffic from passing successfully.

For example, run the following to open your editor and change the Gateway listener's hostname to bar.example.com:

kubectl -n default edit gateway gateway

Once changed, try running the same curl requests as above. They should be denied with a 404 Not Found.