KUMA is installed using the Ansible tool and a YML inventory file. The installation is performed from the control machine, and all of the KUMA components are installed on target machines.
To install KUMA:
cd kuma-ansible-installer
The key file must be named license.key.
sudo cp <key file>.key <installer directory>/roles/kuma/files/license.key
sudo ./install.sh distributed.inventory.yml
If privilege elevation on the target machine requires specifying a password, run the following command and specify the password when prompted:
sudo ./install.sh single.inventory.yml --ask-become-pass
If you do not accept the terms and conditions of the End User License Agreement, the application cannot be installed.
Depending on the type of license activation, the installer produces one of the following results:
installer directory>/roles/kuma/files/ directory, running the installer with the distributed.inventory.yml inventory file installs the KUMA Core on the server from the kuma_core group, additional KUMA Cores are installed on servers from the kuma_core_peers group, all services and OOTB resources specified in the inventory file are installed.To install the services, specify the license code on the command line. Then run the postinstall.sh installer with the "distrtibuter.inventory.yml" inventory file.
sudo ./postinstall.sh distributed.inventory.yml
This creates the specified services. You can select the resources that you want to import from the repository.
The address of the KUMA web interface is https://<FQDN of the host where KUMA is installed>:7220.
Default login credentials:
- login: admin
- password: mustB3Ch@ng3d!
After logging in for the first time, change the password of the admin account
All KUMA components are installed and you are logged in to the web interface.
Subsequently, when installing KUMA services, you can specify multiple comma-separated URLs in the installation command to connect to the KUMA Core services in the Raft cluster.
If you are not using a load balancer in the Raft cluster, you can log in to a KUMA Core node directly. As you go from node to node, whenever you successfully authenticate on the next node, the session opened on the previous node is closed. You can use the balancer to distribute the user load in the Raft cluster, avoiding the need to authenticate on each node.
All servers on which KUMA Core services are deployed must have the same time zone.
We recommend backing up the inventory file that you used to install the program. You can use this inventory file to add components to the system or remove KUMA.
Page top