Walkthrough text updates and quickstart cleanup fix

Kuadrant · Feb 1, 2024 · a72868f · a72868f
1 parent d2e05a0
commit a72868f
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 5 deletions.
diff --git a/docs/how-to/multicluster-gateways-walkthrough.md b/docs/how-to/multicluster-gateways-walkthrough.md
@@ -9,11 +9,11 @@ We will start with a hub cluster and 2 workload clusters and highlight the autom
 
 ## Requirements
 
-- Complete the [Getting Started Guide](https://docs.kuadrant.io/getting-started/).
+- Complete the [Getting Started - Multi Cluster Guide](https://docs.kuadrant.io/getting-started-multi-cluster/).
 
 ## Initial Setup
 
-In this walkthrough, we'll deploy test echo services across multiple clusters. If you followed the [Getting Started Guide](https://docs.kuadrant.io/getting-started/), you would have already set up a `KUADRANT_ZONE_ROOT_DOMAIN` environment variable. For this tutorial, we'll derive a host from this domain for these echo services.
+In this walkthrough, we'll deploy test echo services across multiple clusters. If you followed the [Getting Started - Multi Cluster Guide](https://docs.kuadrant.io/getting-started-multi-cluster/), you would have already set up a `KUADRANT_ZONE_ROOT_DOMAIN` environment variable. For this tutorial, we'll derive a host from this domain for these echo services.
 
 ### Create a gateway
 
@@ -202,7 +202,7 @@ The listener is configured to use this TLS secret also. So now our gateway has b
 
 So now we have workload ingress clusters configured with the same Gateway. 
 
-5. Let's create the HTTPRoute in the first workload cluster. Again, remembering to replace the hostname accordingly if you haven't already set a value for the `KUADRANT_ZONE_ROOT_DOMAIN` variable as described in the [Getting Started Guide](https://docs.kuadrant.io/getting-started/):
+5. Let's create the HTTPRoute in the first workload cluster. Again, remembering to replace the hostname accordingly if you haven't already set a value for the `KUADRANT_ZONE_ROOT_DOMAIN` variable as described in the [Getting Started - Multi Cluster Guide](https://docs.kuadrant.io/getting-started-multi-cluster/):
     ```bash
     kubectl --context kind-mgc-workload-1 apply -f - <<EOF
     apiVersion: gateway.networking.k8s.io/v1
@@ -340,4 +340,4 @@ If you want you can use ```watch dig echo.$KUADRANT_ZONE_ROOT_DOMAIN``` to see t
 Here are some good, follow-on guides that build on this walkthrough:
 
 * [Simple RateLimitPolicy for App Developers](./simple-ratelimitpolicy-for-app-developers.md)
-* [Deploying/Configuring Metrics.](../how-to/metrics-walkthrough.md)
+* [Deploying/Configuring Metrics.](../how-to/metrics-walkthrough.md)
diff --git a/hack/quickstart-cleanup.sh b/hack/quickstart-cleanup.sh
@@ -3,4 +3,5 @@ export KIND_CLUSTER_PREFIX="mgc-"
 
 source /dev/stdin <<< "$(curl -s https://raw.githubusercontent.com/Kuadrant/multicluster-gateway-controller/main/hack/.cleanupUtils)"
 
-cleanup
+cleanupMGC
+cleanupKind