github
/
consul
mirror of https://github.com/hashicorp/consul
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Update website/content/docs/connect/cluster-peering/k8s.mdx

Browse Source 
Co-authored-by: Tu Nguyen <im2nguyen@users.noreply.github.com>
pull/14114/head
Jeff Boruszak 2 years ago committed by GitHub
parent e940842476
commit 26dff8e493
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File

2
website/content/docs/connect/cluster-peering/k8s.mdx
Unescape View File

@ -9,7 +9,7 @@ description: >-
~> **Cluster peering is currently in beta:** Functionality associated
with cluster peering is subject to change. You should never use the beta release in secure environments or production scenarios. Features in
beta may have performance issues, scaling issues, and limited support.<br /><br />Cluster peering is not currently available in the HCP Consul offering.
beta may have performance issues, scaling issues, and limited support.<br/><br/>Cluster peering is not currently available in the HCP Consul offering.
To establish a cluster peering connection on Kubernetes, you need to enable the feature in the Helm chart and create custom resource definitions (CRDs) for each side of the peering.

Write Preview
Loading…
Cancel
Save