I recently needed to deploy an external windows worker. This turned out to require a lot of patching if one starts off with external-worker.yml manifest. While the ops files for windows-worker.yml and windows-worker-ephemeral-disk.yml will add the necessary sections to the manifest, because they are assumed largely to apply to the main concourse deployment, and not an external deployment, one still needs to manually craft an ops file to do the following things:
remove the linux worker and stemcell definitions if they aren't needed
add in the necessary properties to enable the remote worker to contact the tsa (worker_gateway.hosts, worker_gateway.host_public_key)
This PR adds a manifest specifically for deploying an external windows worker, taking inspiration and attempting to follow the pattern set in external-worker.yml.
It's still compatible with windows-worker-ephemeral-disk.yml if it is needed.
vito
commented
4 years ago
Hi!
I recently needed to deploy an external windows worker. This turned out to require a lot of patching if one starts off with
external-worker.ymlmanifest. While the ops files forwindows-worker.ymlandwindows-worker-ephemeral-disk.ymlwill add the necessary sections to the manifest, because they are assumed largely to apply to the main concourse deployment, and not an external deployment, one still needs to manually craft an ops file to do the following things:tsa(worker_gateway.hosts,worker_gateway.host_public_key)This PR adds a manifest specifically for deploying an external windows worker, taking inspiration and attempting to follow the pattern set in
external-worker.yml.It's still compatible with
windows-worker-ephemeral-disk.ymlif it is needed.