You are browsing documentation for a version of Kuma that is not the latest release.
Looking for even older versions? Learn more.
This page exposes the different requirements to run Kuma.
Kuma supports machines with
Kuma is validated against Kubernetes
1.23.x. For the specific Kubernetes version refer to the Kuma CircleCI configuration file.
Versions of envoy supported are:
~1.22.0 which means
You can find the current version in the version.sh file.
Sizing your control-plane
In short, a control-plane with 4vCPU and 2GB of memory will be able to accommodate more than 1000 data planes.
While it’s really hard to give a precise number, a good rule of thumb is to assign about 1MB of memory per data plane. When it comes to CPUs Kuma handles parallelism extremely well (its architecture uses a lot of shared nothing go-routines) so more CPUs usually enable quicker propagation of changes.
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:
- propagation time (xds_delivery): this is the time it takes between a change in the mesh and the dataplane receiving its updated configuration. Think about it as the “reactivity of your mesh”.
- 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 fine-tuning section of the docs.
Sizing your sidecar container on Kubernetes
When deploying Kuma on Kubernetes, the sidecar is deployed as a separate container,
kuma-sidecar, in your
Pods. By default it has the following resource requests and limits:
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
- op: add
you could modify the entire
- op: add
for how to apply these resources to specific
Note: When changing these resources, remember that they must be described using Kubernetes resource units