Deploy a standalone control plane

This is the standard installation method as described in the .

With zone egress:

It’s possible to run ZoneEgress for standalone deployment. In order to deploy Kuma with ZoneEgress run the install command with an additional parameter.

With zone egress:

ZoneEgress works for Universal deployment as well. In order to deploy for Universal deployment .

Once Kuma is up and running, data plane proxies can now connect directly to it.

Optional: Docker authentication

Running administrative tasks (like generating a dataplane token) requires authentication by token or a connection via localhost.

Localhost authentication

For kuma-cp to recognize requests issued to docker published port it needs to run the container in the host network. To do this, add --network="host" parameter to the command.

Authenticate via token

You can also configure kumactl to access kuma-dp from the container. Get the kuma-cp container id:

Control plane offline

  • New data planes proxis won’t be able to join the mesh.
  • Communication between data planes proxies will still work.

You can think of this failure case as “Freezing” the zone mesh configuration. Communication will still work but changes will not be reflected on existing data plane proxies.