status-im/consul
2
0
Fork 0
mirror of https://github.com/status-im/consul.git synced 2025-01-10 22:06:20 +00:00
Code Issues Projects Releases Wiki Activity

docs: add Core requirements to cluster peering k8s docs (#13569)

Browse Source 
* docs: add Core requirements to cluster peering k8s docs

Co-authored-by: trujillo-adam <47586768+trujillo-adam@users.noreply.github.com>
This commit is contained in:
David Yu 2022-06-22 19:12:08 -07:00 committed by GitHub
parent e00ebbb87d
commit a0b94d9a3a
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -21,14 +21,17 @@ The following Custom Resource Definitions (CRDs) are used to create and manage a
## Prerequisites
To create and use cluster peering connections with Kubernetes, you need at least two Kubernetes clusters running in a flat network with Consul on Kubernetes v.0.45 or later.
You must implement the following requirements to create and use cluster peering connections with Kubernetes:
- Consul 1.13 Alpha 2 or later
- At least two Kubernetes clusters
- The Kubernetes clusters must be running in a flat network
- The network must be running on Consul on Kubernetes v.0.45 or later
### Helm chart configuration
To establish cluster peering through Kubernetes, deploy clusters with the following Helm values.
<CodeTabs heading="values.yaml">
<CodeBlockConfig lineNumbers>
<CodeBlockConfig filename="values.yaml">
```yaml
global:
@ -43,7 +46,6 @@ meshGateway:
```
</CodeBlockConfig>
</CodeTabs>
Install Consul on Kubernetes on each Kubernetes cluster by applying `values.yaml` using the Helm CLI.