From 136d3126e01658a032efe6c7d7accd037920cc21 Mon Sep 17 00:00:00 2001 From: Nitya Dhanushkodi Date: Wed, 15 Jun 2022 09:49:33 -0700 Subject: [PATCH] Add changelog for cluster peering (#1279) --- CHANGELOG.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/CHANGELOG.md b/CHANGELOG.md index 4747e6f38f..4063e63c4a 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,5 +1,20 @@ ## UNRELEASED +FEATURES: +* [Experimental] Cluster Peering: Support Consul cluster peering, which allows service connectivity between two independent clusters. + [[GH-1273](https://github.com/hashicorp/consul-k8s/pull/1273)] + + Enabling peering will deploy the peering controllers and PeeringAcceptor and PeeringDialer CRDs. The new CRDs are used + to establish a peering connection between two clusters. + + See the [Cluster Peering on Kubernetes](https://www.consul.io/docs/connect/cluster-peering/k8s) + for full instructions. + + Requirements: + * Consul 1.13+ + * `global.peering.enabled=true` and `connectInject.enabled=true` must be set to enable peering. + * Mesh gateways are required for service to service communication across peers, i.e `meshGateway.enabled=true`. + IMPROVEMENTS: * Helm * Enable the configuring of snapshot intervals in the client snapshot agent via `client.snapshotAgent.interval`. [[GH-1235](https://github.com/hashicorp/consul-k8s/pull/1235)]