Cycloid Workers

There are several ways to deploy your own workers, it can differ a bit if you subscribe to Cycloid Platform (opens new window):

• SaaS console console.cycloid.io (opens new window)
• On-premises setup

All methods rely on the source code of the public stack-external-worker (opens new window).

Prerequisites

Depending of your pipeline jobs, workers generally need access to docker hub to get resource images and access to your code repository.

Exhaustive list of outgoing traffic from the workers:

Required	Service	Destination
yes	Scheduler API	https://scheduler.cycloid.io
yes	Scheduler	scheduler.cycloid.io:32223
yes	Docker registry	https://index.docker.io, docker.io
yes	Cycloid stack	https://github.com/

Required	Service	Destination
yes	Scheduler API	Concourse web https://<cycloid_scheduler>:8443
yes	Scheduler	Concourse TSA <cycloid_scheduler>:2222
yes	Docker registry	https://index.docker.io, docker.io
yes	Cycloid stack	https://github.com/

How to deploy

Provider	Information
	On AWS with CloudFormation
	On Azure with Resource Manager Template
	On Flexible Engine with Resource Template Service (RTS)
	On GCP with Deployment manager
	On baremetal servers
	Locally using Docker (DEVELOPMENT PURPOSES ONLY)

Troubleshooting

If your worker is not running correctly, you can follow the Troubleshooting section.