fix: test fixes for fastpaths modules

- getting-started/finish.md: skip kubectl --watch in automated tests (test=false)
- developer/ebs: add kubectl wait before exec to handle Auto Mode node provisioning delay
- developer/ingress: fix test hook looking for wrong ingress name (ui -> ui-auto)

Author: svennam92

website/docs/fastpaths/developer/ebs/deployment-with-ebs.md

@@ -143,7 +143,13 @@ The volume uses gp3 storage with encryption enabled.
 
 ## Test data persistence
 
-Let's verify that data persists across pod restarts. Create a test file in the MySQL data directory:
+Let's verify that data persists across pod restarts. First, wait for the pod to be ready:
+
+```bash timeout=240
+$ kubectl wait --for=condition=Ready -n catalog pod/catalog-mysql-0 --timeout=180s
+```
+
+Create a test file in the MySQL data directory:
 
 ```bash
 $ kubectl exec -n catalog catalog-mysql-0 -- bash -c "echo 123 > /var/lib/mysql/test.txt"

website/docs/fastpaths/developer/ingress/tests/hook-add-ingress.sh

@@ -7,7 +7,7 @@ before() {
 after() {
   sleep 20
 
-  export ui_endpoint=$(kubectl get ingress -n ui ui -o json | jq -r '.status.loadBalancer.ingress[0].hostname')
+  export ui_endpoint=$(kubectl get ingress -n ui ui-auto -o json | jq -r '.status.loadBalancer.ingress[0].hostname')
 
   if [ -z "$ui_endpoint" ]; then
     >&2 echo "Failed to retrieve hostname from Ingress"

website/docs/fastpaths/getting-started/finish.md

@@ -28,7 +28,7 @@ As you deploy additional workloads, EKS Auto Mode will automatically provision a
 
 Watch as EKS Auto Mode provisions a node for your workload. You'll see EKS Auto Mode provision a second node in the general-purpose node pool for our applications. It will also consolidate the system node as there is capacity to move the pods around.
 
-```bash timeout=180
+```bash timeout=180 test=false
 $ kubectl get nodes --watch
 ...
 NAME                  STATUS     ROLES    AGE   VERSION