From ada3dc9c196b4f16c644c40c7dea78b6e14cf0ff Mon Sep 17 00:00:00 2001 From: David Yu Date: Fri, 12 Aug 2022 09:00:04 -0700 Subject: [PATCH] docs: bumping requirements for cluster peering to consul k8s 0.47.0 and 1.13.1 (#14177) --- website/content/docs/connect/cluster-peering/k8s.mdx | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/website/content/docs/connect/cluster-peering/k8s.mdx b/website/content/docs/connect/cluster-peering/k8s.mdx index 26d86cf312..4986a61b13 100644 --- a/website/content/docs/connect/cluster-peering/k8s.mdx +++ b/website/content/docs/connect/cluster-peering/k8s.mdx @@ -21,10 +21,10 @@ The following CRDs are used to create and manage a peering connection: ## Prerequisites 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 - 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 @@ -34,7 +34,7 @@ To establish cluster peering through Kubernetes, deploy clusters with the follow ```yaml global: - image: "hashicorp/consul:1.13.0" + image: "hashicorp/consul:1.13.1" peering: enabled: true connectInject: @@ -55,7 +55,7 @@ $ export HELM_RELEASE_NAME=cluster-name ``` ```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