The Mesh resource lets you create multiple isolated service meshes within the same Kong Mesh cluster, allowing you to operate in environments that require more than one mesh for security, segmentation, or governance reasons.
You can create a mesh per line of business, per team, per application, or per environment. Multiple meshes allow organizations to adopt a service mesh gradually without requiring all teams to coordinate, and provide an extra layer of security and segmentation. For example, policies applied to one mesh don’t affect other meshes.
Mesh is the parent resource of every other resource in Kong Mesh, including:
To use Kong Mesh, at least one mesh must exist. There is no limit to the number of meshes that can be created.
When a data plane proxy connects to the control plane (kuma-cp), it specifies which Mesh resource it belongs to. A data plane proxy can only belong to one mesh at a time.
When starting a new Kong Mesh cluster from scratch, a
defaultmesh is created automatically.
In addition to creating virtual service meshes, the Mesh resource is also used for:
- Mutual TLS, to secure and encrypt service traffic and assign an identity to the data plane proxies within the mesh.
-
Zone egress, to define whether
ZoneEgressshould be used for cross-zone and external service communication. -
Non-mesh traffic, to define whether
passthroughmode should be used for the non-mesh traffic.
If you need cross-mesh communication, you must use an intermediary API Gateway. For more information, see Built-in gateways in Kong Mesh.