From 618c7f14b0d304067d0820020b5d29b44d981be8 Mon Sep 17 00:00:00 2001 From: Nitya Dhanushkodi Date: Mon, 20 Jun 2022 09:16:31 -0700 Subject: [PATCH] add peering helm value --- website/content/docs/k8s/helm.mdx | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/website/content/docs/k8s/helm.mdx b/website/content/docs/k8s/helm.mdx index 53274177a2..9d3037ea3a 100644 --- a/website/content/docs/k8s/helm.mdx +++ b/website/content/docs/k8s/helm.mdx @@ -61,6 +61,12 @@ Use these links to navigate to a particular top-level stanza. (see `-domain` (https://www.consul.io/docs/agent/config/cli-flags#_domain)) and the domain services synced from Consul into Kubernetes will have, e.g. `service-name.service.consul`. + - `peering` ((#v-global-peering)) - [Experimental] Configures the Cluster Peering feature. Requires Consul v1.13+ and Consul-K8s v0.45+. + + - `enabled` ((#v-global-peering-enabled)) (`boolean: false`) - If true, the Helm chart will enable Cluster Peering for the cluster. This will enable peering controllers and + allow use of the PeeringAcceptor and PeeringDialer CRDs to establish peerings for service mesh. + @type boolean + - `adminPartitions` ((#v-global-adminpartitions)) - Enabling `adminPartitions` allows creation of Admin Partitions in Kubernetes clusters. It additionally indicates that you are running Consul Enterprise v1.11+ with a valid Consul Enterprise license. Admin partitions enables deploying services across partitions, while sharing