You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: website/content/docs/connect/cluster-peering/configuration.mdx
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,15 +5,15 @@ description: >-
5
5
6
6
---
7
7
8
-
# Enabling Service-to-service Traffic Across Peered Clusters
8
+
# Cluster Peering Configuration
9
9
10
-
The topic provides an overview of the configuration options and process for cluster peering.
10
+
This topic provides an overview of the configuration options when creating cluster peering. Use these options to enable service-to-service traffic Across Peered Clusters
11
11
12
12
## Prerequisites
13
13
14
14
To configure mesh gateways for cluster peering, make sure your Consul environment meets the following requirements:
15
15
16
-
- Consul version 1.14.0 or newer.
16
+
- Consul v1.14 or higher.
17
17
- A local Consul agent is required to manage mesh gateway configuration.
18
18
- Use [Envoy proxies](/docs/connect/proxies/envoy). Envoy is the only proxy with mesh gateway capabilities in Consul.
Copy file name to clipboardExpand all lines: website/content/docs/connect/cluster-peering/index.mdx
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,6 +29,7 @@ You can find specific cluster peering configuration and usage information in the
29
29
- To manage or delete existing cluster peering connections, refer to [Manage cluster peering connections](/consul/docs/cluster-peering/usage/manage-connections).
30
30
- To set up service failovers and redirects, refer to [L7 traffic management for cluster peering connections](/consul/docs/cluster-peering/usage/peering-traffic-management).
31
31
- To use cluster peering with Kubernetes deployments, refer to [Cluster peering on Kubernetes](/consul/docs/cluster-peering/usage/k8s).
32
+
- To use cluster peering with HCP Consul, refer to [Cluster peering in the HCP documentation](/hcp/docs/consul/usage/cluster-peering).
32
33
33
34
> To learn how to peer clusters and connect services across peers in AWS Elastic Kubernetes Service (EKS) environments, complete the [Consul Cluster Peering on Kubernetes tutorial](/consul/tutorials/developer-mesh/cluster-peering-aws).
Copy file name to clipboardExpand all lines: website/content/docs/connect/cluster-peering/usage/create-cluster-peering.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,7 +29,7 @@ Mesh gateways are required for you to route service mesh traffic between partiti
29
29
- A cluster requires a registered mesh gateway in order to export services to peers.
30
30
- For Enterprise, this mesh gateway must also be registered in the same partition as the exported services and their `exported-services` configuration entry.
31
31
- To use the `local` mesh gateway mode, you must register a mesh gateway in the importing cluster.
32
-
-
32
+
33
33
## Create a peering token
34
34
35
35
To begin the cluster peering process, generate a peering token in one of your clusters. The other cluster uses this token to establish the peering connection.
Copy file name to clipboardExpand all lines: website/content/docs/connect/cluster-peering/usage/k8s.mdx
+6-7Lines changed: 6 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,9 +7,10 @@ description: >-
7
7
8
8
# Cluster Peering on Kubernetes
9
9
10
-
To establish a cluster peering connection on Kubernetes, you need to enable several pre-requisite values in the Helm chart and create custom resource definitions (CRDs) for each side of the peering.
10
+
To establish a cluster peering connection on Kubernetes, you need to enable several values in the Helm chart and create custom resource definitions (CRDs) for each side of the peering.
11
+
12
+
All peering connection traffic, including both data plane and control plane traffic, is routed through mesh gateways. As a result, the following Helm values for mesh gateways are mandatory for cluster peering:
11
13
12
-
The following Helm values are mandatory for cluster peering:
@@ -18,18 +19,15 @@ The following CRDs are used to create and manage a peering connection:
18
19
-`PeeringAcceptor`: Generates a peering token and accepts an incoming peering connection.
19
20
-`PeeringDialer`: Uses a peering token to make an outbound peering connection with the cluster that generated the token.
20
21
21
-
Peering connections, including both data plane and control plane traffic, is routed through mesh gateways.
22
-
As of Consul v1.14, you can also [implement service failovers and redirects to control traffic](/consul/docs/connect/l7-traffic) between peers.
23
-
24
22
> To learn how to peer clusters and connect services across peers in AWS Elastic Kubernetes Service (EKS) environments, complete the [Consul Cluster Peering on Kubernetes tutorial](https://learn.hashicorp.com/tutorials/consul/cluster-peering-aws?utm_source=docs).
25
23
26
24
## Prerequisites
27
25
28
26
You must implement the following requirements to create and use cluster peering connections with Kubernetes:
29
27
30
-
- Consul v1.14.0 or later
28
+
- Consul v1.14 or higher
31
29
- At least two Kubernetes clusters
32
-
- The installation must be running on Consul on Kubernetes version 1.0.0 or later
30
+
- The installation must be running on Consul on Kubernetes v1.0.0 or later
33
31
34
32
### Prepare for installation
35
33
@@ -97,6 +95,7 @@ the servers for that cluster. The servers for `cluster-02` will use that informa
97
95
`cluster-01`. Complete the following steps to create the peer connection.
98
96
99
97
### Using mesh gateways for the peering connection
98
+
100
99
If the servers in `cluster-01` are not directly routable from the dialing cluster `cluster-02`, then you'll need to set up peering through mesh gateways.
101
100
102
101
1. In `cluster-01` apply the `Mesh` custom resource so the generated token will have the mesh gateway addresses which will be routable from the other cluster.
0 commit comments