Careful!

You are browsing documentation for a version of Kuma that is not the latest release.

Docker

To install and run Kuma on Docker execute the following steps:

1. Download Kuma
2. Run Kuma
3. Use Kuma

The official Docker images are used by default in the Kubernetes and OpenShift distributions.

1. Download Kuma

Kuma provides the following Docker images for all of its executables:

kuma-cp: at docker.io/kumahq/kuma-cp:{"edition"=>"kuma", "version"=>"2.9.0", "release"=>"2.9.x", "latest"=>true, "releaseDate"=>"2024-10-22", "endOfLifeDate"=>"2025-10-22", "branch"=>"release-2.9"}
kuma-dp: at docker.io/kumahq/kuma-dp:{"edition"=>"kuma", "version"=>"2.9.0", "release"=>"2.9.x", "latest"=>true, "releaseDate"=>"2024-10-22", "endOfLifeDate"=>"2025-10-22", "branch"=>"release-2.9"}
kumactl: at docker.io/kumahq/kumactl:{"edition"=>"kuma", "version"=>"2.9.0", "release"=>"2.9.x", "latest"=>true, "releaseDate"=>"2024-10-22", "endOfLifeDate"=>"2025-10-22", "branch"=>"release-2.9"}

You can freely docker pull these images to start using Kuma, as we will demonstrate in the following steps.

2. Run Kuma

We can run Kuma:

docker run -p 5681:5681 docker.io/kumahq/kuma-cp:{"edition"=>"kuma", "version"=>"2.9.0", "release"=>"2.9.x", "latest"=>true, "releaseDate"=>"2024-10-22", "endOfLifeDate"=>"2025-10-22", "branch"=>"release-2.9"} run

This example will run Kuma in standalone mode for a “flat” deployment, but there are more advanced deployment modes like “multi-zone”.

Note: By default this will run Kuma with a memory store, but you can use a persistent storage like PostgreSQL by updating the conf/kuma-cp.conf file.

2.1 Authentication (optional)

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

2.1.1 Localhost

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 docker run command from point 2.

2.1.2 Authenticating via token

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

docker ps # copy kuma-cp container id

export KUMA_CP_CONTAINER_ID='...'

Configure kumactl:

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

3. Use Kuma

Kuma (kuma-cp) is now running! Now that Kuma has been installed you can access the control-plane via either the GUI, the HTTP API, or the CLI:

Kuma ships with a read-only GUI that you can use to retrieve Kuma resources. By default the GUI listens on the API port and defaults to :5681/gui.

To access Kuma you can navigate to 127.0.0.1:5681/gui to see the GUI.

You can use the kumactl CLI to perform read and write operations on Kuma resources. The kumactl binary is a client to the Kuma HTTP API. For example:

docker run --net="host" kumahq/kumactl:<version> kumactl get meshes
NAME          mTLS      METRICS      LOGGING   TRACING
default       off       off          off       off

or you can enable mTLS on the default Mesh with:

echo "type: Mesh
name: default
mtls:
  enabledBackend: ca-1
  backends:
  - name: ca-1
    type: builtin" | docker run -i --net="host" \
  docker.io/kumahq/kumactl:<version> kumactl apply -f -

Note: we are running kumactl from the Docker container on the same network as the host, but most likely you want to download a compatible version of Kuma for the machine where you will be executing the commands.

You can run the following script to automatically detect the operating system and download Kuma:

curl -L https://kuma.io/installer.sh | sh -

or you can download the distribution manually:

<a href=”https://packages.konghq.com/public/kuma-legacy/raw/names/kuma-centos-amd64/versions/{“edition”=>”kuma”, “version”=>”2.9.0”, “release”=>”2.9.x”, “latest”=>true, “releaseDate”=>”2024-10-22”, “endOfLifeDate”=>”2025-10-22”, “branch”=>”release-2.9”}/kuma-{“edition”=>”kuma”, “version”=>”2.9.0”, “release”=>”2.9.x”, “latest”=>true, “releaseDate”=>”2024-10-22”, “endOfLifeDate”=>”2025-10-22”, “branch”=>”release-2.9”}-centos-amd64.tar.gz”>CentOS</a>
<a href=”https://packages.konghq.com/public/kuma-legacy/raw/names/kuma-rhel-amd64/versions/{“edition”=>”kuma”, “version”=>”2.9.0”, “release”=>”2.9.x”, “latest”=>true, “releaseDate”=>”2024-10-22”, “endOfLifeDate”=>”2025-10-22”, “branch”=>”release-2.9”}/kuma-{“edition”=>”kuma”, “version”=>”2.9.0”, “release”=>”2.9.x”, “latest”=>true, “releaseDate”=>”2024-10-22”, “endOfLifeDate”=>”2025-10-22”, “branch”=>”release-2.9”}-rhel-amd64.tar.gz”>RedHat</a>
<a href=”https://packages.konghq.com/public/kuma-legacy/raw/names/kuma-debian-amd64/versions/{“edition”=>”kuma”, “version”=>”2.9.0”, “release”=>”2.9.x”, “latest”=>true, “releaseDate”=>”2024-10-22”, “endOfLifeDate”=>”2025-10-22”, “branch”=>”release-2.9”}/kuma-{“edition”=>”kuma”, “version”=>”2.9.0”, “release”=>”2.9.x”, “latest”=>true, “releaseDate”=>”2024-10-22”, “endOfLifeDate”=>”2025-10-22”, “branch”=>”release-2.9”}-debian-amd64.tar.gz”>Debian</a>
<a href=”https://packages.konghq.com/public/kuma-legacy/raw/names/kuma-ubuntu-amd64/versions/{“edition”=>”kuma”, “version”=>”2.9.0”, “release”=>”2.9.x”, “latest”=>true, “releaseDate”=>”2024-10-22”, “endOfLifeDate”=>”2025-10-22”, “branch”=>”release-2.9”}/kuma-{“edition”=>”kuma”, “version”=>”2.9.0”, “release”=>”2.9.x”, “latest”=>true, “releaseDate”=>”2024-10-22”, “endOfLifeDate”=>”2025-10-22”, “branch”=>”release-2.9”}-ubuntu-amd64.tar.gz”>Ubuntu</a>
<a href=”https://packages.konghq.com/public/kuma-legacy/raw/names/kuma-darwin-amd64/versions/{“edition”=>”kuma”, “version”=>”2.9.0”, “release”=>”2.9.x”, “latest”=>true, “releaseDate”=>”2024-10-22”, “endOfLifeDate”=>”2025-10-22”, “branch”=>”release-2.9”}/kuma-{“edition”=>”kuma”, “version”=>”2.9.0”, “release”=>”2.9.x”, “latest”=>true, “releaseDate”=>”2024-10-22”, “endOfLifeDate”=>”2025-10-22”, “branch”=>”release-2.9”}-darwin-amd64.tar.gz”>macOS</a> or run brew install kumactl

and extract the archive with:

tar xvzf kuma-*.tar.gz

You will then find the kumactl executable in the kuma-{"edition"=>"kuma", "version"=>"2.9.0", "release"=>"2.9.x", "latest"=>true, "releaseDate"=>"2024-10-22", "endOfLifeDate"=>"2025-10-22", "branch"=>"release-2.9"}/bin folder.

You will notice that Kuma automatically creates a Mesh entity with name default.

4. Quickstart

Congratulations! You have successfully installed Kuma on Docker 🚀.

In order to start using Kuma, it’s time to check out the quickstart guide for Universal deployments. If you are using Docker you may also be interested in checking out the Kubernetes quickstart as well.

← OpenShift Amazon Linux →