From 1b0e20a681e64a9af2f8e10169a0cd0d6d4c03f8 Mon Sep 17 00:00:00 2001 From: David Yu <dyu@hashicorp.com> Date: Tue, 29 Nov 2022 13:49:54 -0600 Subject: [PATCH] docs: typo on cluster peering k8s (#15602) --- 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 4ea2ec5161..aca908977a 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=<CONTEXT for second Kubernetes cluster> ``` -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. <CodeBlockConfig filename="values.yaml"> @@ -249,7 +249,7 @@ like to configure the mesh gateway mode such that this traffic always leaves thr </CodeBlockConfig> ```shell-session - $ kubectl --context $CLUSTER1_CONTEXT apply -f proxy-defaults.yaml + $ kubectl --context $CLUSTER2_CONTEXT apply -f proxy-defaults.yaml ``` ### Export services between clusters