kasmtech
Custom Agent, Kubernetes and other compute
Hi All,
First time here :)
For a project I am doing, I want to create and provision my own instances as a response to user selection. These instances need to be provisioned when the user selects the instance type - much like the behavior of the docker agent. In general, we would need to provision machines on,
- Cloud compute (AWS, GCP.. etc)
- Windows machines.
- Kubernetes pods.
- Docker containers.
- Podman (We are considering it).
I was wondering if there was a way to create a "custom" agent, one which accepts a webhook and would return a running machine and the container status to workspaces. In this project we require making custom provisioning. Agent would provide,
- Status
- Machine details.
- Actions (Delete, create, etc)
- Other requirements...
E.g. the workflow would be,
- User selects the container/machine type
- A webhook is sent to the agent to create the machine,
- Agent returns with status running
- User sees machine provisioned or error, and can start working.
Hi, We don't have a generic interface to create your own custom agent role via webhooks.
However Kasm Workspaces can be deployed across multiple Deployment Zones ( https://kasmweb.com/docs/latest/guide/zones/deployment_zones.html#deployment-zones) which in your case might mean one Zone in AWS, another in GCP, another on prem.
We have AutoScale providers with can automatically provision our Docker Agent role and aribitrary VMs (E.g Windows machines) in various cloud providers and hypervisors like vSphere, OpenStack and coming in the next version Harvester HCI & Kubevirt. You can configure the system to create a standby pool of Agents/VMs, schedule them to scale up according to schedules or create machines fully on demand . https://kasmweb.com/docs/latest/guide/compute/pools.html
We’re currently enhancing our GitHub issue tracker to improve organization and efficiency.
As part of this process, we’re closing older issues to help keep the tracker focused on current and active topics.
If this issue is still relevant or you’re still experiencing the problem, please feel free to create a new issue.
Thank you for your understanding!
