From a0b94d9a3a13eef869a098d0e36e46fb4b00462b Mon Sep 17 00:00:00 2001 From: David Yu Date: Wed, 22 Jun 2022 19:12:08 -0700 Subject: [PATCH] docs: add Core requirements to cluster peering k8s docs (#13569) * docs: add Core requirements to cluster peering k8s docs Co-authored-by: trujillo-adam <47586768+trujillo-adam@users.noreply.github.com> --- website/content/docs/connect/cluster-peering/k8s.mdx | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/website/content/docs/connect/cluster-peering/k8s.mdx b/website/content/docs/connect/cluster-peering/k8s.mdx index 0fca618871..b39c58ee8f 100644 --- a/website/content/docs/connect/cluster-peering/k8s.mdx +++ b/website/content/docs/connect/cluster-peering/k8s.mdx @@ -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. - - + ```yaml global: @@ -43,7 +46,6 @@ meshGateway: ``` - Install Consul on Kubernetes on each Kubernetes cluster by applying `values.yaml` using the Helm CLI.