From c5dd81e2c1543ff0d11a1c828cbb37891c5e8e70 Mon Sep 17 00:00:00 2001 From: hc-github-team-consul-core Date: Tue, 29 Nov 2022 14:51:16 -0500 Subject: [PATCH] Backport of docs: typo on cluster peering k8s into release/1.14.x (#15604) Co-authored-by: David Yu --- website/content/docs/connect/cluster-peering/k8s.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/content/docs/connect/cluster-peering/k8s.mdx b/website/content/docs/connect/cluster-peering/k8s.mdx index 7bcd713b2e75..72df62f9e8d5 100644 --- a/website/content/docs/connect/cluster-peering/k8s.mdx +++ b/website/content/docs/connect/cluster-peering/k8s.mdx @@ -47,7 +47,7 @@ Complete the following procedure after you have provisioned a Kubernetes cluster $ export CLUSTER2_CONTEXT= ``` -1. To establish cluster peering through Kubernetes, create a `values.yaml` file with the following Helm values. **NOTE:** Mesh Gateway replicas are defaulted to 1 replica, and could be adjusted using the `meshGateway.replicas` value for higher availaibity. +1. To establish cluster peering through Kubernetes, create a `values.yaml` file with the following Helm values. **NOTE:** Mesh Gateway replicas are defaulted to 1 replica, and could be adjusted using the `meshGateway.replicas` value for higher availability. @@ -249,7 +249,7 @@ like to configure the mesh gateway mode such that this traffic always leaves thr ```shell-session - $ kubectl --context $CLUSTER1_CONTEXT apply -f proxy-defaults.yaml + $ kubectl --context $CLUSTER2_CONTEXT apply -f proxy-defaults.yaml ``` ### Export services between clusters