Docker

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

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

    • kuma-cp: at
    • kuma-dp: at kong-docker-kuma-docker.bintray.io/kuma-dp:1.1.1
    • kuma-prometheus-sd: at kong-docker-kuma-docker.bintray.io/kuma-prometheus-sd:1.1.1

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

    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:

    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.

    To learn more, read the .

    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.

    Kuma () 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 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:5681Docker - 图2 (opens new window) to see the HTTP API.

    or you can enable mTLS on the Mesh with:

    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:

    or you can download the distribution manually:

    and extract the archive with:

    You will then find the kumactl executable in the kuma-1.1.1/bin folder.

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

    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 as well.