From c798db392dae55d07fc442fef455af77d5851d46 Mon Sep 17 00:00:00 2001 From: boruszak Date: Tue, 2 Aug 2022 14:26:20 -0500 Subject: [PATCH] Initial new features commit --- website/content/docs/connect/cluster-peering/index.mdx | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/website/content/docs/connect/cluster-peering/index.mdx b/website/content/docs/connect/cluster-peering/index.mdx index a50dd26992..0b6ee7af0f 100644 --- a/website/content/docs/connect/cluster-peering/index.mdx +++ b/website/content/docs/connect/cluster-peering/index.mdx @@ -37,6 +37,13 @@ Regardless of whether you connect your clusters through WAN federation or cluste | Uses gossip protocol | ✅ | ❌ | ## Beta release features and constraints + +The cluster peering beta adds the following features and functions: + +- You can generate peering tokens, establish, list, read, and delete peerings, and manage intentions for peering connections with both the API and the UI. +- You can configure [transparent proxies](/docs/connect/transparent-proxy) for peered services. +- You can use the [`peering` rule for ACL enforcement](/docs/security/acl/acl-rules#peering) of peering APIs. + Not all features and functionality are available in the beta release. In particular, consider the following technical constraints: - Mesh gateways for _server to server traffic_ are not available. However, mesh gateways for _service to service traffic_ between clusters are available.