Configuring your mesh and multi-tenancy

Uses: Kong Mesh
Related Documentation
Minimum Version
Kong Mesh - 2.6

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 default mesh 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 ZoneEgress should be used for cross-zone and external service communication.
  • Non-mesh traffic, to define whether passthrough mode 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.

Creating a mesh

To create a Mesh resource, you only need to specify a name:

Creating resources in a mesh

When creating other resources, you can add them to the mesh in the following ways.

Data plane proxies

When starting a data plane proxy, specify which mesh it belongs to:

You can control which data plane proxies are allowed to join the mesh using mesh constraints.

Policies

When creating new policies, you must also specify which mesh they belong to:

Default resources

To help users get started, Kong Mesh creates the following default policies:

  • MeshTimeout for all gateways
  • MeshTimeout for all sidecar resources
  • MeshRetry
  • MeshCircuitBreaker

Skipping default resource creation

To prevent these policies from being added when creating a mesh, set skipCreatingInitialPolicies:

You can also skip creating the default mesh by setting the following parameter when configuring the control plane: KUMA_DEFAULTS_SKIP_MESH_CREATION=true.

Mesh schema

Help us make these docs great!

Kong Developer docs are open source. If you find these useful and want to make them better, contribute today!