![]() ![]() Once the runner pod is created, the runner application in the pod uses the JIT configuration token to register itself with the GitHub Actions Service. ![]() After 24 hours the GitHub Actions Service unassigns the job if no runner accepts it. If the pod's status is failed, the controller retries up to 5 times. The controller attempts to create runner pods. The Ephemeral RunnerSet attempts to create new runners and the EphemeralRunner Controller requests a Just-in-Time (JIT) configuration token to register these runners.The Runner ScaleSet Listener uses a Service Account and a Role bound to that account to make an HTTPS call through the Kubernetes APIs to patch the Ephemeral RunnerSet resource with the number of desired replicas count.If it can, the Runner ScaleSet Listener acknowledges the message. When the Runner ScaleSet Listener receives the Job Available message, it checks whether it can scale up to the desired count.When a workflow run is triggered from a repository, the GitHub Actions Service dispatches individual job runs to the runners or runner scalesets where the runs-on key matches the name of the runner scaleset or labels of self-hosted runners.The listener stays idle until it receives a Job Available message from the GitHub Actions Service. ![]() In this pod, the listener application connects to the GitHub Actions Service to authenticate and establish an HTTPS long poll connection.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |