Docker
To install and run Kuma on Docker execute the following steps:
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
kong-docker-kuma-docker.bintray.io/kuma-cp:1.1.2
- kuma-dp: at
kong-docker-kuma-docker.bintray.io/kuma-dp:1.1.2
- kumactl: at
kong-docker-kuma-docker.bintray.io/kumactl:1.1.2
- kuma-prometheus-sd: at
kong-docker-kuma-docker.bintray.io/kuma-prometheus-sd:1.1.2
You can freely docker pull
these images to start using Kuma, as we will demonstrate in the following steps.
2. Run Kuma
Finally we can run Kuma in either standalone or multi-zone mode:
Standalone mode is perfect when running Kuma in a single cluster across one environment:
$ docker run \
-p 5681:5681 \
kong-docker-kuma-docker.bintray.io/kuma-cp:1.1.2 run
To learn more, read about the deployment modes available.
Multi-zone mode is perfect when running one deployment of Kuma that spans across multiple Kubernetes clusters, clouds and VM environments under the same Kuma deployment.
This mode also supports hybrid Kubernetes + VMs deployments.
To learn more, read the multi-zone installation instructions.
Note: By default this will run Kuma with a memory
backend, but you can use a persistent storage like PostgreSQL by updating the conf/kuma-cp.conf
file.
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
(opens new window) to see the GUI.
Kuma ships with a read and write HTTP API that you can use to perform operations on Kuma resources. By default the HTTP API listens on port 5681
.
To access Kuma you can navigate to 127.0.0.1:5681
(opens new window) to see the HTTP API.
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" \
kong-docker-kuma-docker.bintray.io/kumactl: 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" \
kong-docker-kuma-docker.bintray.io/kumactl: 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:
- CentOS (opens new window)
- RedHat (opens new window)
- Debian (opens new window)
- Ubuntu (opens new window)
- macOS (opens new window)
and extract the archive with:
$ tar xvzf kuma-*.tar.gz
You will then find the kumactl
executable in the kuma-1.1.2/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.