Debian

    Finally, you can follow the Quickstart to take it from here and continue your Kuma journey.

    Run the following script to automatically detect the operating system and download Kuma:

    or you can download the distribution manually.

    Then extract the archive with: .

    Make sure you have tar and gzip installed.

    Once downloaded, you will find the contents of Kuma in the kuma-2.1.1 folder. In this folder, you will find - among other files - the bin directory that stores all the executables for Kuma.

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

    We suggest adding the kumactl executable to your so that it’s always available in every working directory. Or - alternatively - you can also create link in /usr/local/bin/ by executing:

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

    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 to see the GUI.

    To access Kuma you can navigate to 127.0.0.1:5681 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:

    or you can enable mTLS on the default Mesh with:

    You can configure kumactl to point to any zone kuma-cp instance by running:

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

    Congratulations! You have successfully installed Kuma 🚀.