Add attached routes notes

Author: Kate Osborn

tests/reconfig/results/1.1.0/1.1.0.md

@@ -65,11 +65,13 @@ NGF deployment:
 
 ## NumResources to Total Resources
 
-| NumResources | Gateways | Secrets | ReferenceGrants | Namespaces | application Pods | application Services | HTTPRoutes | Total Resources |
-|--------------|----------|---------|-----------------|------------|------------------|----------------------|------------|-----------------|
-| x            | 1        | 1       | 1               | x+1        | 2x               | 2x                   | 3x         | <total>         |
-| 30           | 1        | 1       | 1               | 31         | 60               | 60                   | 90         | 244             |
-| 150          | 1        | 1       | 1               | 151        | 300              | 300                  | 450        | 1204            |
+| NumResources | Gateways | Secrets | ReferenceGrants | Namespaces | application Pods | application Services | HTTPRoutes | Attached HTTPRoutes | Total Resources |
+|--------------|----------|---------|-----------------|------------|------------------|----------------------|------------|---------------------|-----------------|
+| x            | 1        | 1       | 1               | x+1        | 2x               | 2x                   | 3x         | 2x                  | <total>         |
+| 30           | 1        | 1       | 1               | 31         | 60               | 60                   | 90         | 60                  | 244             |
+| 150          | 1        | 1       | 1               | 151        | 300              | 300                  | 450        | 300                 | 1204            |
+
+> Note: Only 2x HTTPRoutes attach to the Gateway because the parentRef name in the `cafe-tls-redirect` HTTPRoute is incorrect. This will be fixed in the next release.
 
 ## Observations
 
@@ -83,3 +85,7 @@ NGF deployment:
 3. No errors (NGF or NGINX) were observed in any test run.
 
 4. The majority of the event batches were processed in 500ms or less except the 3rd test. In the 3rd test, we create the Gateway resource after all the apps and routes. The batch that contains the Gateway is the only one that takes longer than 500ms. It takes ~13s.
+
+## Future Improvements
+
+1. Fix the parentRef name in the `cafe-tls-redirect` [HTTPRoute](/tests/reconfig/scripts/cafe-routes.yaml), so it matches the deployed Gateway.

tests/reconfig/setup.md

@@ -58,13 +58,17 @@
       - Note: Clean up after each test run for isolated results. There's a script provided for removing all the test
         fixtures `scripts/delete-multiple.sh` which takes a number (needs to be the same number as what was used in the
         create script.)
-5. After each individual test run, grab logs of both NGF containers and grab metrics.
-   Note: You can expose metrics by running the below snippet and then navigating to `127.0.0.1:9113/metrics`:
-
-   ```console
-   GW_POD=$(k get pods -n nginx-gateway | sed -n '2s/^\([^[:space:]]*\).*$/\1/p')
-   kubectl port-forward $GW_POD -n nginx-gateway 9113:9113 &
-   ```
+5. After each individual test:
+    - Describe the Gateway resource and make sure the status is correct.
+    - Check the logs of both NGF containers for errors.
+    - Parse the logs for TimeToReady numbers (see steps 6-7 below).
+    - Grab metrics.
+      Note: You can expose metrics by running the below snippet and then navigating to `127.0.0.1:9113/metrics`:
+
+       ```console
+       GW_POD=$(k get pods -n nginx-gateway | sed -n '2s/^\([^[:space:]]*\).*$/\1/p')
+       kubectl port-forward $GW_POD -n nginx-gateway 9113:9113 &
+       ```
 
 6. Measure NGINX Reloads and Time to Ready Results
    1. TimeToReadyTotal as described in each test - NGF logs.
@@ -90,7 +94,7 @@
       e.g. `cd scripts && bash create-resources-gw-last.sh 30`. The script will deploy backend apps and services, wait
       60 seconds for them to be ready, and deploy 1 Gateway, 1 RefGrant, 1 Secret, and HTTPRoutes.
    2. Deploy NGF
-   3. Measure TimeToReadyTotal as the time it takes from start-up -> config written and
+   3. Measure TimeToReadyTotal as the time it takes from start-up -> final config written and
       NGINX reloaded. Measure the other results as described in steps 6-7 of the [Setup](#setup) section.
 
 ### Test 2: Start NGF, deploy Gateway, create many resources attached to GW