From 6aaf6743965da8aa5f6778ea363c8a0d141c6c51 Mon Sep 17 00:00:00 2001 From: boruszak Date: Mon, 1 Aug 2022 10:43:38 -0500 Subject: [PATCH] Beta release constraints updated --- .../docs/connect/cluster-peering/index.mdx | 15 ++++++--------- 1 file changed, 6 insertions(+), 9 deletions(-) diff --git a/website/content/docs/connect/cluster-peering/index.mdx b/website/content/docs/connect/cluster-peering/index.mdx index 7393b448e8..f943a2d935 100644 --- a/website/content/docs/connect/cluster-peering/index.mdx +++ b/website/content/docs/connect/cluster-peering/index.mdx @@ -31,20 +31,17 @@ Regardless of whether you connect your clusters through WAN federation or cluste | Connects clusters across datacenters | ✅ | ✅ | | Shares support queries and service endpoints | ✅ | ✅ | | Connects clusters owned by different operators | ❌ | ✅ | -| Functions without declaring primary datacenter | ❌ | ✅ | +| Functions without declaring primary datacenter | ❌ | ✅ | | Shares key/value stores | ✅ | ❌ | | Uses gossip protocol | ✅ | ❌ | -## Technical preview constraints -Not all features and functionality are available in the technical preview release. In particular, consider the following technical constraints: +## Beta release constraints +Not all features and functionality are available in the beta release. In particular, consider the following technical constraints: -- Consul ACLs must be disabled or the ACL `default_policy` must be set to `allow`. - Mesh gateways for _server to server traffic_ are not available. However, mesh gateways for _service to service traffic_ between clusters are available. -- Services exported to peered clusters must be configured to use the TCP protcol (not HTTP, HTTP 2 and gRPC). -- Support for dynamic routing such as splits, custom routes, or redirects is not available. +- Dynamic routing features such as splits, custom routes, and redirects cannot target services in a peered cluster. +- Configuring service failover across peers is not supported for service mesh. +- Consul datacenters that are already federated stay federated. You do not need to migrate WAN federated clusters to cluster peering. - The `consul intention CLI` command is not supported. To manage intentions that specify services in peered clusters, use [configuration entries](/docs/connect/config-entries/service-intentions). -- [L7 permissions](/docs/connect/l7-traffic) are not supported. -- Configuring service failover across peers is not supported. - Accessing key/value stores across peers is not supported. -- Consul datacenters that are already federated stay federated. - Non-enterprise Consul instances cannot sync services with namespaces outside of the `default` namespace.