status-im
/
consul
mirror of https://github.com/status-im/consul.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

docs: bumping requirements for cluster peering to consul k8s 0.47.0 and 1.13.1 (#14177)

This commit is contained in:
David Yu 2022-08-12 09:00:04 -07:00 committed by GitHub
parent c6de7e413f
commit ada3dc9c19
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -21,10 +21,10 @@ The following CRDs are used to create and manage a peering connection:
## Prerequisites ## Prerequisites
You must implement the following requirements to create and use cluster peering connections with Kubernetes: You must implement the following requirements to create and use cluster peering connections with Kubernetes:
- Consul version 1.13.0 or later - Consul version 1.13.1 or later
- At least two Kubernetes clusters - At least two Kubernetes clusters
- The Kubernetes clusters must be running in a flat network - The Kubernetes clusters must be running in a flat network
- The network must be running on Consul on Kubernetes version 0.45 or later - The network must be running on Consul on Kubernetes version 0.47.0 or later
### Helm chart configuration ### Helm chart configuration
@ -34,7 +34,7 @@ To establish cluster peering through Kubernetes, deploy clusters with the follow
```yaml ```yaml
global: global:
image: "hashicorp/consul:1.13.0" image: "hashicorp/consul:1.13.1"
peering: peering:
enabled: true enabled: true
connectInject: connectInject:
@ -55,7 +55,7 @@ $ export HELM_RELEASE_NAME=cluster-name
``` ```
```shell-session ```shell-session
$ helm install ${HELM_RELEASE_NAME} hashicorp/consul --version "0.45.0" --values values.yaml $ helm install ${HELM_RELEASE_NAME} hashicorp/consul --version "0.47.0" --values values.yaml
``` ```
## Create a peering token ## Create a peering token