Debian

    Finally you can follow the 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 (opens new window) the distribution manually.

    Then extract the archive with:

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

      So we enter the bin folder by executing:

      Finally we can run Kuma in either standalone or multi-zone mode:

      1. $ ./kuma-cp run

      To learn more, read about the .

      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.

      We suggest adding the kumactl executable to your PATH 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 , but you can 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:

      To access Kuma you can navigate to 127.0.0.1:5681/guiDebian - 图2 (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 to see the HTTP API.

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

      1. $ kumactl get meshes
      2. NAME          mTLS      METRICS      LOGGING   TRACING

      or you can enable mTLS on the default Mesh with:

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

      1. $ kumactl config control-planes add --name=XYZ --address=http://{address-to-kuma}:5681

      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 deployments.