From cc5cbcba7c10616f17de1cf14b5f65626f838bdc Mon Sep 17 00:00:00 2001 From: David Yu Date: Tue, 25 Apr 2023 09:42:31 -0700 Subject: [PATCH] Update single-dc-multi-k8s.mdx (#17126) --- .../docs/k8s/deployment-configurations/single-dc-multi-k8s.mdx | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/website/content/docs/k8s/deployment-configurations/single-dc-multi-k8s.mdx b/website/content/docs/k8s/deployment-configurations/single-dc-multi-k8s.mdx index 46fc2228016a..4f23ccddabe9 100644 --- a/website/content/docs/k8s/deployment-configurations/single-dc-multi-k8s.mdx +++ b/website/content/docs/k8s/deployment-configurations/single-dc-multi-k8s.mdx @@ -15,7 +15,8 @@ This example uses two Kubernetes clusters, but this approach could be extended t ## Requirements -* Consul-Helm version `v1.0.0` or higher +* `consul-k8s` v1.0.x or higher, and Consul 1.14.x or higher +* Kubernetes clusters must be able to communicate over LAN on a flat network. * Either the Helm release name for each Kubernetes cluster must be unique, or `global.name` for each Kubernetes cluster must be unique to prevent collisions of ACL resources with the same prefix. ## Prepare Helm release name ahead of installs