CP/DP Split: Update documentation on accessing nginx container (#3338)

Update documentation on accessing nginx container

Problem: With our incoming changes to our control data plane split, the nginx container will no longer be in the NGF Pod. Thus all documentation on accessing the nginx container (logs, sending traffic, config...) need to be updated.

Solution: Updated the documentation. Mainly, when sending traffic in the examples, the host and IP of the NGINX Service are recorded after the Gateway is deployed. Most of these changes are in our examples.

Author: bjee19

docs/developer/testing.md

@@ -69,19 +69,19 @@ Follow the steps below for manual testing:
    - Logs of the `nginx-gateway` container. Look out for unexpected error logs or panics.
 
      ```shell
-     kubectl logs -n nginx-gateway -l app=nginx-gateway
+     kubectl -n nginx-gateway logs <ngf-pod-name> -c nginx-gateway
      ```
 
    - Logs of the `nginx` container. Look for unexpected error logs and verify the access logs are correct.
 
      ```shell
-     kubectl logs -n nginx-gateway -l app=nginx
+     kubectl -n <nginx-pod-namespace> logs <nginx-pod-name> -c nginx
      ```
 
    - The generated nginx config. Make sure it's correct.
 
      ```shell
-     kubectl exec -it -n nginx-gateway <nginx gateway pod> -c nginx -- nginx -T
+     kubectl exec -it -n <nginx-pod-namespace> <nginx-pod-name> -c nginx -- nginx -T
      ```
 
    - The statuses of the Gateway API Resources. Make sure they look correct.

examples/cafe-example/README.md

@@ -9,18 +9,6 @@ to route traffic to that application using HTTPRoute resources.
 
 1. Follow the [installation instructions](https://docs.nginx.com/nginx-gateway-fabric/installation/) to deploy NGINX Gateway Fabric.
 
-1. Save the public IP address of NGINX Gateway Fabric into a shell variable:
-
-   ```text
-   GW_IP=XXX.YYY.ZZZ.III
-   ```
-
-1. Save the port of NGINX Gateway Fabric:
-
-   ```text
-   GW_PORT=<port number>
-   ```
-
 ## 2. Deploy the Cafe Application
 
 1. Create the coffee and the tea Deployments and Services:
@@ -49,6 +37,15 @@ to route traffic to that application using HTTPRoute resources.
    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:
+
+    ```text
+    GW_IP=XXX.YYY.ZZZ.III
+    GW_PORT=<port number>
+    ```
+
 1. Create the HTTPRoute resources:
 
    ```shell

examples/cross-namespace-routing/README.md

@@ -9,18 +9,6 @@ in a different namespace from our HTTPRoutes.
 
 1. Follow the [installation instructions](https://docs.nginx.com/nginx-gateway-fabric/installation/) to deploy NGINX Gateway Fabric.
 
-1. Save the public IP address of NGINX Gateway Fabric into a shell variable:
-
-   ```text
-   GW_IP=XXX.YYY.ZZZ.III
-   ```
-
-1. Save the port of NGINX Gateway Fabric:
-
-   ```text
-   GW_PORT=<port number>
-   ```
-
 ## 2. Deploy the Cafe Application
 
 1. Create the cafe namespace and cafe application:
@@ -49,6 +37,15 @@ in a different namespace from our HTTPRoutes.
    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:
+
+    ```text
+    GW_IP=XXX.YYY.ZZZ.III
+    GW_PORT=<port number>
+    ```
+
 1. Create the HTTPRoute resources:
 
    ```shell

examples/grpc-routing/README.md

@@ -9,18 +9,6 @@ to route traffic to that application using GRPCRoute resources.
 
 1. Follow the [installation instructions](https://docs.nginx.com/nginx-gateway-fabric/installation/) to deploy NGINX Gateway Fabric.
 
-1. Save the public IP address of NGINX Gateway Fabric into a shell variable:
-
-    ```text
-    GW_IP=XXX.YYY.ZZZ.III
-    ```
-
-1. Save the port of NGINX Gateway Fabric:
-
-    ```text
-    GW_PORT=<port number>
-    ```
-
 ## 2. Deploy the Helloworld Application
 
 1. Create the two helloworld Deployments and Services:
@@ -60,7 +48,16 @@ There are 3 options to configure gRPC routing. To access the application and tes
     kubectl apply -f exact-method.yaml
     ```
 
-2. Test the Application:
+    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:
+
+    ```text
+    GW_IP=XXX.YYY.ZZZ.III
+    GW_PORT=<port number>
+    ```
+
+1. Test the Application:
 
     ```shell
     grpcurl -plaintext -proto grpc.proto -authority bar.com -d '{"name": "exact"}' ${GW_IP}:${GW_PORT} helloworld.Greeter/SayHello
@@ -72,7 +69,7 @@ There are 3 options to configure gRPC routing. To access the application and tes
     }
     ```
 
-3. Clean up the Gateway and GRPCRoute resources:
+1. Clean up the Gateway and GRPCRoute resources:
 
     ```shell
     kubectl delete -f exact-method.yaml
@@ -86,7 +83,16 @@ There are 3 options to configure gRPC routing. To access the application and tes
     kubectl apply -f hostname.yaml
     ```
 
-2. Test the Application:
+    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:
+
+    ```text
+    GW_IP=XXX.YYY.ZZZ.III
+    GW_PORT=<port number>
+    ```
+
+1. Test the Application:
 
     ```shell
     grpcurl -plaintext -proto grpc.proto -authority bar.com -d '{"name": "bar server"}' ${GW_IP}:${GW_PORT} helloworld.Greeter/SayHello
@@ -132,7 +138,7 @@ There are 3 options to configure gRPC routing. To access the application and tes
     2024/04/29 09:29:46 Received: foo bar server
     ```
 
-3. Clean up the Gateway and GRPCRoute resources:
+1. Clean up the Gateway and GRPCRoute resources:
 
     ```shell
     kubectl delete -f hostname.yaml
@@ -146,7 +152,16 @@ There are 3 options to configure gRPC routing. To access the application and tes
     kubectl apply -f headers.yaml
     ```
 
-2. Test the Application:
+    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:
+
+    ```text
+    GW_IP=XXX.YYY.ZZZ.III
+    GW_PORT=<port number>
+    ```
+
+1. Test the Application:
 
     ```shell
     grpcurl -plaintext -proto grpc.proto -authority bar.com -d '{"name": "version one"}' -H 'version: one' ${GW_IP}:${GW_PORT} helloworld.Greeter/SayHello
@@ -230,7 +245,7 @@ There are 3 options to configure gRPC routing. To access the application and tes
    2024/04/29 09:33:26 Received: version two orange
    ```
 
-3. Clean up the Gateway and GRPCRoute resources:
+1. Clean up the Gateway and GRPCRoute resources:
 
    ```shell
    kubectl delete -f headers.yaml