adding fixes

This commit is contained in:
David Yu 2022-06-21 16:27:06 -07:00
parent 63d5f90832
commit 3124a9245b
1 changed files with 7 additions and 2 deletions

View File

@ -29,6 +29,7 @@ To establish cluster peering through Kubernetes, deploy clusters with the follow
<CodeTabs heading="values.yaml"> <CodeTabs heading="values.yaml">
<CodeBlockConfig lineNumbers> <CodeBlockConfig lineNumbers>
```yaml ```yaml
global: global:
image: "hashicorp/consul:1.13.0-alpha2" image: "hashicorp/consul:1.13.0-alpha2"
@ -39,14 +40,18 @@ connectInject:
meshGateway: meshGateway:
enabled: true enabled: true
replicas: 1 replicas: 1
```
</CodeBlockConfig> </CodeBlockConfig>
</CodeTabs> </CodeTabs>
Install Consul on Kubernetes using the values file `values.yaml` using the Helm CLI. Install Consul on Kubernetes on each Kubernetes cluster by applying `values.yaml` using the Helm CLI.
```shell-session ```shell-session
$ export HELM_RELEASE_NAME=peer1 $ export HELM_RELEASE_NAME=cluster-name
$ helm install ${HELM_RELEASE_NAME} hashicorp/consul --version "0.45.0" --values server.yaml $ helm install ${HELM_RELEASE_NAME} hashicorp/consul --version "0.45.0" --values server.yaml
```
## Create a peering connection ## Create a peering connection
To peer Kubernetes clusters running Consul, you need to create a peering token and share it with the other cluster. To peer Kubernetes clusters running Consul, you need to create a peering token and share it with the other cluster.