Browse Source

Apply suggestions from code review

Co-authored-by: trujillo-adam <47586768+trujillo-adam@users.noreply.github.com>
docs-cluster-peering-technical-preview^2
Jeff Boruszak 2 years ago committed by GitHub
parent
commit
40e5d8b0ae
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
  1. 4
      website/content/docs/connect/cluster-peering/index.mdx

4
website/content/docs/connect/cluster-peering/index.mdx

@ -40,10 +40,10 @@ Not all features and functionality are available in the technical preview releas
- Mesh gateways for _service to service traffic_ between clusters are available. However, mesh gateways for _server to server traffic_ are not available. - Mesh gateways for _service to service traffic_ between clusters are available. However, mesh gateways for _server to server traffic_ are not available.
- Services exported to peered clusters must not be configured as HTTP. - Services exported to peered clusters must not be configured as HTTP.
- Support for dynamic routing such as splits, custom routes, or redirects is not available at this time. - Support for dynamic routing such as splits, custom routes, or redirects is not available.
- The `consul intention CLI` command is not supported. - The `consul intention CLI` command is not supported.
- [L7 permissions](/docs/connect/l7-traffic) are not supported. - [L7 permissions](/docs/connect/l7-traffic) are not supported.
- Configuring service failover across peers is not supported. - Configuring service failover across peers is not supported.
- Accessing key/value stores across peers is not supported. - Accessing key/value stores across peers is not supported.
- Consul datacenters that are already federated stay federated. - Consul datacenters that are already federated stay federated.
- Non-enterprise Consul instances cannot sync services with namespaces outside of the default namespace. - Non-enterprise Consul instances cannot sync services with namespaces outside of the `default` namespace.

Loading…
Cancel
Save