Skip to content

Commit

Permalink
fixes
Browse files Browse the repository at this point in the history
Signed-off-by: Charly Molter <[email protected]>
  • Loading branch information
lahabana committed Nov 13, 2023
1 parent 6a774a9 commit afac32b
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions app/_posts/2023-11-14-kuma-2-5-0.md
Original file line number Diff line number Diff line change
Expand Up @@ -41,11 +41,11 @@ Check to blogpost above, the [MADR](https://github.com/kumahq/kuma/blob/master/d

## inferring reachable services from `MeshTrafficPermission`

Service Meshes suffer from the fact that default they enable a fully connected graph of services.
Service Meshes by default enable a fully connected graph of services.
This is problematic as we can't naively optimize which instance of the mesh needs to know of which services.
The result of this is growing size of configuration and sidecar footprint becoming important.

For while we've addressed this problem with [reachable services](https://docs.konghq.com/mesh/latest/production/upgrades-tuning/fine-tuning/#reachable-services).
For a while we've addressed this problem with [reachable services](https://docs.konghq.com/mesh/latest/production/upgrades-tuning/fine-tuning/#reachable-services).
However, this can be hard to manage in large setups without strong central deployment processes.
What we've noticed is that [`MeshTrafficPermissions`](https://kuma.io/docs/2.5.x/policies/meshtrafficpermission/) can help us do some pruning and reduce the complexity of this graph.

Expand All @@ -63,7 +63,7 @@ We will keep working in this community to further improve service mesh support i
## Delta KDS as default

KDS (Kuma discovery service) is the protocol based on [Envoy XDS](https://www.envoyproxy.io/docs/envoy/v1.28.0/api-docs/xds_protocol#xds-protocol) which we use to synchronize global control-planes and zonal control-planes.
As the size of Kuma installation grow the resource consumption could grow significantly and resource consumption could be undesirably big.
As the size of Kuma installations grow the resource consumption has grown significantly and resource consumption can become undesirably big.
We've released the first version of our rewrite of KDS in 2.3.0 and we believe that the protocol is now ready to be used by default.

The transition from the old to the new protocol is seamless so you don’t have to worry about it.
Expand Down

0 comments on commit afac32b

Please sign in to comment.