Adding an Agent to a Single Server Install
The following instructions can be used to install an additional Kasm Agent to a pre-existing Single Server installation of Kasm Workspaces.
Instructions
Open a terminal on the single-server Kasm installation and stop the Kasm Services.
sudo /opt/kasm/bin/stop
Modify the
api.app.config.yaml
. Change theserver.server_hostname
setting to the local IP address of your single server Kasm installation (e.g192.168.56.107
).
Depending on the architecture and may be more appropriate to utilize an FQDN but ultimately the new agent must be able to connect to and resolve this address. In this guide we will assume all systems are on the same LAN where the single-server resides at192.168.56.107
.sudo nano /opt/kasm/current/conf/app/api.app.config.yaml
Start the services on the single server Kasm Installation
sudo /opt/kasm/bin/start
Back inside the Kasm Admin UI, you should see that the Manager is now reporting with the local IP previously configured.
Updating Zone Settings
In the Kasm Admin UI, expand Infrastructure, Select Zones, then click Edit next to the default zone.
Change the Upstream Auth Address to the local IP of the installation (e.g
192.168.56.107
) then click Save.
Agent Installation
Login to the Admin UI, select Settings → Global . Find the Manager section, and copy the Token value. This will be used in installation of the Agent. e.g (
971FaRQXp8c4zUJbBWSQ
).Follow the official instructions for installing and enabling an Agent on a standalone server: Multi Server Installation — Kasm 1.16.1 documentation . Utilize the local IP of the single server (e.g
192.168.56.107
) as the--manager-hostname
value. For example:sudo bash kasm_release/install.sh --role agent --public-hostname [AGENT_HOSTNAME] --manager-hostname 192.168.56.107 --manager-token 971FaRQXp8c4zUJbBWSQ
Related Docs:
Related articles