These scripts are example startup scripts that may be used for autoscaling Servers and Docker Agents in a Kasm Workspaces deployment.
Note
For versions compatible with older releases of Kasm Workspaces, please check the corresponding release branches.
Kasm Workspaces can auto-scale full stack VMs and add them to a Server Pool. You may want to add startup scripts to the VM to take actions on boot. For example, for a Windows server you may need to join it to Active Directory. For a Linux Server you may need to install and configure KasmVNC.
Kasm Workspaces can auto-scale Docker Agents and join them to the cluster in order to fulfill client sessions of containerized desktops and applications. The VMs you spin up can be base Ubuntu images that are maintained by the Cloud Service Provider and the startup scripts can install Docker and the Kasm agent. This project provides example startup scripts you can use your auto scaled deployments. We attempt to have a single script that will work on any of the supported cloud providers.
Each VM provider caps how large a startup script (user data) can be. Larger scripts are hosted and downloaded by a small bootstrap instead of pasted in full.
| Platform | Limit |
|---|---|
| AWS (EC2) | 16 KB (16,384 bytes), tightest of all |
| OCI (Oracle Cloud) | 16 KB user data (32 KB total with other metadata) |
| Azure | 64 KB |
| DigitalOcean | 64 KiB |
| OpenStack | 64 KB |
| vSphere | 64,000 bytes |
| GCP | 256 KB |
| Nutanix, Proxmox, KubeVirt, Harvester | No fixed cap; user data is delivered via a mounted disk / snippet / Kubernetes Secret, not a small metadata field |
Figures vary by region/API version; confirm against current provider docs.