RedHat
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 the distribution manually.
Then extract the archive with:
Once downloaded, you will find the contents of Kuma in the kuma-0.5.1
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:
$ ./kuma-cp run
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:
Kuma ships with a read-only GUI that you can use to retrieve Kuma resources. By default the GUI listens on port 5683
.
To access Kuma you can navigate to 127.0.0.1:5683
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
.
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:
$ kumactl get meshes
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:
$ 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
.
Congratulations! You have successfully installed Kuma on RedHat 🚀.
In order to start using Kuma, it’s time to check out the quickstart guide for Universal deployments.