401f3010e0
This config entry is being renamed primarily because in k8s the name cluster could be confusing given that the config entry applies across federated datacenters. Additionally, this config entry will only apply to Consul as a service mesh, so the more generic "cluster" name is not needed.
3 lines
77 B
Plaintext
3 lines
77 B
Plaintext
```release-note:improvement
|
|
connect: rename cluster config entry to mesh.
|
|
``` |