You are browsing documentation for a version of Kuma that is not the latest release.
Looking for even older versions? Learn more.
Deploy a standalone control plane
In order to deploy Kuma in a standalone deployment, the
kuma-cp control plane must be started in
This is the standard installation method.
kumactl install control-plane \ --set "controlPlane.mode=standalone" \ | kubectl apply -f -
With zone egress:
It’s possible to run
for standalone deployment. In order to deploy Kuma with
ZoneEgress run the install command with an additional parameter.
Once Kuma is up and running, data plane proxies can now connect directly to it.
When the mode is not specified, Kuma will always start in
standalone mode by default.
Optional: control plane authentication
Running administrative tasks (like generating a dataplane token) requires authentication by token or a connection via localhost when interacting with the control plane.
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
docker run command.
Authenticate via token
You can also configure
kumactl to access
kuma-dp from the container.
kuma-cp container id:
docker ps # copy kuma-cp container id export KUMA_CP_CONTAINER_ID='...'
TOKEN=$(bash -c "docker exec -it $KUMA_CP_CONTAINER_ID wget -q -O - http://localhost:5681/global-secrets/admin-user-token" | jq -r .data | base64 -d) kumactl config control-planes add \ --name my-control-plane \ --address http://localhost:5681 \ --auth-type=tokens \ --auth-conf token=$TOKEN \ --skip-verify