mirror of https://github.com/status-im/consul.git
/docs/connect/gateways/mesh-gateways
This commit is contained in:
parent
f60da88228
commit
ebcb557ebf
|
@ -1,12 +1,11 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Service-to-service Traffic Across Datacenters
|
||||
page_title: Mesh Gateways between Datacenters
|
||||
description: >-
|
||||
This topic describes how to configure mesh gateways to route a service's data to upstreams
|
||||
in other datacenters. It describes how to use Envoy and how you can integrate with your preferred gateway.
|
||||
Mesh gateways are specialized proxies that route data between services that cannot communicate directly with upstreams. Learn how to enable service-to-service traffic across datacenters and review example configuration entries.
|
||||
---
|
||||
|
||||
# Service-to-service Traffic Across Datacenters
|
||||
# Mesh Gateways between Datacenters
|
||||
|
||||
-> **1.6.0+:** This feature is available in Consul versions 1.6.0 and newer.
|
||||
|
||||
|
|
|
@ -1,12 +1,11 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Service-to-service Traffic Across Partitions
|
||||
page_title: Mesh Gateways between Admin Partitions
|
||||
description: >-
|
||||
This topic describes how to configure mesh gateways to route a service's data to upstreams
|
||||
in other partitions. It describes how to use Envoy and how you can integrate with your preferred gateway.
|
||||
Mesh gateways are specialized proxies that route data between services that cannot communicate directly with upstreams. Learn how to enable service-to-service traffic across admin partitions and review example configuration entries.
|
||||
---
|
||||
|
||||
# Service-to-service Traffic Across Partitions
|
||||
# Mesh Gateways between Admin Partitions
|
||||
|
||||
-> **Consul Enterprise 1.11.0+:** Admin partitions are supported in Consul Enterprise versions 1.11.0 and newer.
|
||||
|
||||
|
|
|
@ -1,12 +1,11 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Service-to-service Traffic Across Peered Clusters
|
||||
page_title: Mesh Gateways between Peered Clusters
|
||||
description: >-
|
||||
This topic describes how to configure mesh gateways to route a service's data to upstreams
|
||||
in clusters that have a peering connection.
|
||||
Mesh gateways are specialized proxies that route data between services that cannot communicate directly with upstreams. Learn how to enable service-to-service traffic across clusters that have an established peering connection.
|
||||
---
|
||||
|
||||
# Service-to-service Traffic Across Peered Clusters
|
||||
# Mesh Gateways between Peered Clusters
|
||||
|
||||
~> **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.
|
||||
|
||||
|
|
|
@ -1,11 +1,11 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: WAN Federation via Mesh Gateways
|
||||
description: |-
|
||||
WAN federation via mesh gateways allows for Consul servers in different datacenters to be federated exclusively through mesh gateways.
|
||||
page_title: Mesh Gateways for WAN Federation
|
||||
description: >-
|
||||
You can use mesh gateways to federate deployments, which enables WAN gossip between agents in different datacenters. Forward service requests, use prepared queries, and replicate key/value entries across geographically separated clusters by configuring a primary datacenter.
|
||||
---
|
||||
|
||||
# WAN Federation via Mesh Gateways
|
||||
# Mesh Gateways for WAN Federation
|
||||
|
||||
-> **1.8.0+:** This feature is available in Consul versions 1.8.0 and higher
|
||||
|
||||
|
|
Loading…
Reference in New Issue