From f96dee3adcbf6b84009204966a4a97f20d03bcaa Mon Sep 17 00:00:00 2001 From: Ashwin Venkatesh Date: Thu, 16 Jun 2022 12:14:03 -0400 Subject: [PATCH] Revert "Add changelog for cluster peering (#1279)" This reverts commit 136d3126e01658a032efe6c7d7accd037920cc21. --- CHANGELOG.md | 15 --------------- 1 file changed, 15 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 4063e63c4a..4747e6f38f 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,20 +1,5 @@ ## 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)]