Remote Agents

swimlane remote agents run automation actions on networks outside your primary swimlane environment agents use outbound secure websockets (tls/443) to turbine connectors and action data travel over that connection; a vpn to the customer network is not required remote agents require a container host ( docker or podman ) you install an agent with the install script from admin panel > settings > tenant > nodes for the full procedure, see installation https //docs swimlane com/installation choose your path i want to… start here understand how remote agents work architecture /#architecture install an agent (including quadlet or override registries) installation https //docs swimlane com/installation view agents and pools viewing remote agents https //docs swimlane com/viewing remote agents assign pools to playbook actions assigning pools to actions https //docs swimlane com/assigning pools to actions uninstall an agent uninstall remote agent https //docs swimlane com/uninstall remote agent architecture remote agents use containers to isolate workloads connectors run as containers inside an internal podman engine, next to a turbine agent container the agent opens an outbound secure websocket to turbine all traffic to the primary instance uses tls/443 during install and upgrade, base images pull from quay io unless you override image locations agents schedule automatic updates with a cron job created at install time older agents can still connect after a platform upgrade; the update job replaces them on the next cron run starting in turbine 26 3 0 , you can install with podman quadlet ( q ) and pull connector images from override registries ( b / c ) see installation https //docs swimlane com/installation related guides installation https //docs swimlane com/installationviewing remote agents https //docs swimlane com/viewing remote agentsassigning pools to actions https //docs swimlane com/assigning pools to actionsuninstall remote agent https //docs swimlane com/uninstall remote agent