Skip to content

Commit

Permalink
Add changelog for cluster peering (#1279)
Browse files Browse the repository at this point in the history
  • Loading branch information
ndhanushkodi authored and thisisnotashwin committed Jun 16, 2022
1 parent dda6be1 commit 136d312
Showing 1 changed file with 15 additions and 0 deletions.
15 changes: 15 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -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)]
Expand Down

0 comments on commit 136d312

Please sign in to comment.