Skip to content
This repository has been archived by the owner on Dec 16, 2024. It is now read-only.

Walkthrough text updates and quickstart cleanup fix #782

Merged
merged 1 commit into from
Feb 2, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions docs/how-to/multicluster-gateways-walkthrough.md
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down Expand Up @@ -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
Expand Down Expand Up @@ -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)
3 changes: 2 additions & 1 deletion hack/quickstart-cleanup.sh
Original file line number Diff line number Diff line change
Expand Up @@ -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
Loading