luxolus
/
open-consul
2
0
Fork 0
Code Issues 1 Pull Requests Packages Releases Wiki Activity

add peering helm value

This commit is contained in:
Nitya Dhanushkodi 2022-06-20 09:16:31 -07:00
parent 6980975d6f
commit 7e8b21a0e0
1 changed files with 6 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
website/content/docs/k8s/helm.mdx
View File

@ -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)) - <EnterpriseAlert inline /> 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