eb5f16caf5
Signed-off-by: Taylor Silva <dev@taydev.net> |
||
|---|---|---|
| .. | ||
| baggageclaim | ||
| integration | ||
| land | ||
| network | ||
| retire | ||
| runtime | ||
| workercmd | ||
| workerfakes | ||
| .gitignore | ||
| README.md | ||
| beacon.go | ||
| beacon_runner.go | ||
| beacon_test.go | ||
| container_sweeper.go | ||
| container_sweeper_test.go | ||
| counting_wait_group.go | ||
| healthchecker.go | ||
| healthchecker_test.go | ||
| signals_unix.go | ||
| signals_windows.go | ||
| suite_test.go | ||
| tsa_client_iface.go | ||
| tsa_config.go | ||
| volume_sweeper.go | ||
README.md
worker
worker - container orchestrator/ worker artifact management/ build executor
from the United States Library of Congress's Prints and Photographs division
about
worker is the workhorse of Concourse. It's responsible for the creation and deletion of the containers in which the pipeline operations (get, check, put, task) are executed.
A worker node registers with the web node(s) and is then used for executing builds and performing resource checks.
The ATC component in the web node(s) decides how to allocate containers to workers that have been registered in the pool, using the configured container-placement-strategy. It also manages the container deletion on the workers via database calls and the Garden API on the workers.
A worker node runs the following 2 GO API's
-
Garden is a generic interface for orchestrating containers remotely on a worker
-
Baggageclaim is a server for managing caches and artifacts on the workers
It can be scaled horizontally in order to scale the system.