Lifecycle of Release Runner
This topic describes the lifecycle, control commands, and the different states of a Release Runner, with regards to the availability of the Release server.
In the Release SaaS Edition, your Release instance includes a cloud-based Release Runner managed by digital.ai that is available for use. On-prem runners are not supported. For more information, see Release SaaS - Limitations.
Readiness and Liveness of Runners
Release Runner has two endpoints for readiness and liveness that checks for the current status of Runner's readiness and liveness respectively. These endpoints are used in the Kubernetes cluster to propagate container events and status.
- Runner is ready if it successfully registers against the Release server
- Runner is alive if the service starts
Additionally, Release server checks for the health of Runner by sending ping control command over an SSE channel. If ping is not received for more than 30 seconds, then the Runner will initiate a health check of the connection towards Release by restarting the SSE channel. In case the health check towards Release fails, the Runner will transition into the Idle state, attempting to recover the connections to Release.
Delete Runners
In case the Release Runner is deleted from the Release server configuration a Delete control command is sent to the Runner. This command will initiate shutdown of the Runner. However, before it's shutdown, it will do a clean-up of any data and configuration stored on the system. At the end of the shutdown process, it will exit and terminate the container.