Skip to content

Commit

Permalink
Backport of docs: typo on cluster peering k8s into release/1.14.x (#1…
Browse files Browse the repository at this point in the history
…5604)

Co-authored-by: David Yu <dyu@hashicorp.com>
  • Loading branch information
hc-github-team-consul-core and david-yu committed Nov 29, 2022
1 parent 9a235cb commit c5dd81e
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions website/content/docs/connect/cluster-peering/k8s.mdx
Expand Up @@ -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">

Expand Down Expand Up @@ -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
Expand Down

0 comments on commit c5dd81e

Please sign in to comment.