From 82f58c5717e215a915de1f14f9018c59f9f5b49b Mon Sep 17 00:00:00 2001 From: David Martin Date: Wed, 1 May 2024 11:52:15 +0100 Subject: [PATCH] Change multi cluster docs link to new location --- docs/gateways/define-and-place-a-gateway.md | 2 +- docs/how-to/multicluster-gateways-walkthrough.md | 6 +++--- docs/installation/control-plane-installation.md | 2 +- 3 files changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/gateways/define-and-place-a-gateway.md b/docs/gateways/define-and-place-a-gateway.md index 42d2394f..f047abb5 100644 --- a/docs/gateways/define-and-place-a-gateway.md +++ b/docs/gateways/define-and-place-a-gateway.md @@ -3,7 +3,7 @@ In this guide, we will go through defining a Gateway in the OCM hub cluster that can then be distributed to and instantiated on a set of managed spoke clusters. ### Prerequisites -* Complete the [Getting Started Guide](https://docs.kuadrant.io/getting-started-multi-cluster/) to bring up a suitable environment. +* Complete the [Getting Started Guide](https://docs.kuadrant.io/getting-started-multi-cluster-ocm/) to bring up a suitable environment. If you are looking to change provider from the default Istio: * Please have the Gateway provider of your choice installed and configured (in this example we use Envoy gateway. See the following [docs](https://gateway.envoyproxy.io/v0.5.0/user/quickstart.html)) diff --git a/docs/how-to/multicluster-gateways-walkthrough.md b/docs/how-to/multicluster-gateways-walkthrough.md index 42c4a74c..e025dae1 100644 --- 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 - Multi Cluster Guide](https://docs.kuadrant.io/getting-started-multi-cluster/). +- Complete the [Getting Started - Multi Cluster Guide](https://docs.kuadrant.io/getting-started-multi-cluster-ocm/). ## Initial Setup -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. +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-ocm/), 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 - Multi Cluster Guide](https://docs.kuadrant.io/getting-started-multi-cluster/): +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-ocm/): ```bash kubectl --context kind-mgc-workload-1 apply -f - <