Requirements

Kuma supports machines with architecture and since 1.7.0 it’s possible to run Kuma on arm64.

Kuma is validated against Kubernetes 1.19.x, 1.20.x, and 1.22.x.

Versions of envoy supported are: ~1.22.0 which means >=1.22.0 and <1.23.0.

In short, a control-plane with 4vCPU and 2GB of memory will be able to accommodate more than 1000 data planes.

That being said we highly recommend you to run your own load tests prior to going to production. There are many ways to run workloads and deploy applications and while we test some of them, you are in the best place to build a realistic benchmark of what you do.

To see if you may need to increase your control-plane’s spec, there are two main metrics to pay attention to:

• configuration generation time (xds_generation): this is the time it takes for the configuration to be generated.

For any large mesh using transparent-proxy it’s highly recommended to use reachable-services .

You can also find tuning configuration in the section of the docs.

This configuration should be enough for most use cases. In some cases, like when you cannot scale horizontally or your service handles lots of concurrent traffic, you may need to change these values. You can do this using the .

For example, you can modify individual parameters under resources:

you could modify the entire limits, request or sections:

Check the ContainerPatch documentation for how to apply these resources to specific Pods.