luxolus
/
open-consul
2
0
Fork 0
Code Issues 1 Pull Requests Packages Releases Wiki Activity

Apply suggestions from code review 

Co-authored-by: David Yu <dyu@hashicorp.com>
Co-authored-by: trujillo-adam <47586768+trujillo-adam@users.noreply.github.com>
This commit is contained in:
Tu Nguyen 2022-06-21 16:13:39 -07:00 committed by GitHub
parent 23e4884779
commit 60f6948b0a
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 11 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
website/content/docs/connect/cluster-peering/k8s.mdx
View File

@ -27,8 +27,11 @@ To create and use cluster peering connections with Kubernetes, you need at least
To establish cluster peering through Kubernetes, deploy clusters with the following Helm values.
<CodeTabs heading="values.yaml">
<CodeBlockConfig lineNumbers>
```yaml
global:
image: "hashicorp/consul:1.13.0-alpha2"
peering:
enabled: true
connectInject:
@ -36,13 +39,19 @@ connectInject:
meshGateway:
enabled: true
replicas: 1
```
</CodeBlockConfig>
</CodeTabs>
Install Consul on Kubernetes using the values file `values.yaml` using the Helm CLI.
```shell-session
$ export HELM_RELEASE_NAME=peer1
$ helm install ${HELM_RELEASE_NAME} hashicorp/consul --version "0.45.0" --values server.yaml
## Create a peering connection
To peer Kubernetes clusters running Consul, you need to create a peering token and share it with the other cluster.
1. In “cluster-01,” create the `PeeringAcceptor` custom resource.
1. In `cluster-01`, create the `PeeringAcceptor` custom resource.
<CodeBlockConfig filename="acceptor.yml">