From a3a4495e78f667c4ab0b42acfa598a0ce98ce322 Mon Sep 17 00:00:00 2001 From: Matt Keeler Date: Fri, 24 Jun 2022 09:58:31 -0400 Subject: [PATCH] Clarify the wording of the peering limitations in the preview (#13590) --- website/content/docs/connect/cluster-peering/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/content/docs/connect/cluster-peering/index.mdx b/website/content/docs/connect/cluster-peering/index.mdx index 73980ceb29..1d23666325 100644 --- a/website/content/docs/connect/cluster-peering/index.mdx +++ b/website/content/docs/connect/cluster-peering/index.mdx @@ -40,7 +40,7 @@ Not all features and functionality are available in the technical preview releas - 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 not be configured as HTTP. +- 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. - 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.