Your Question
Hi, I'm using Tartelet for self-hosted runners and I'm seeing a behavior that I'm not sure is a misconfiguration on my part.
When a runner is launched and registered with GitHub to wait for a job, if no job is assigned within the runner registration token's expiration window, the runner becomes a 'zombie'—it's still running on the VM but is no longer connected to GitHub.
My understanding is that Tartelet's ephemeral design should prevent this, as a runner should only be spun up when a job is available. Could you confirm if this behavior is indicative of a misconfiguration on my end and what setting I should check to ensure Tartelet is only launching runners for pending jobs?
Any additional context?
No response
Your Question
Hi, I'm using Tartelet for self-hosted runners and I'm seeing a behavior that I'm not sure is a misconfiguration on my part.
When a runner is launched and registered with GitHub to wait for a job, if no job is assigned within the runner registration token's expiration window, the runner becomes a 'zombie'—it's still running on the VM but is no longer connected to GitHub.
My understanding is that Tartelet's ephemeral design should prevent this, as a runner should only be spun up when a job is available. Could you confirm if this behavior is indicative of a misconfiguration on my end and what setting I should check to ensure Tartelet is only launching runners for pending jobs?
Any additional context?
No response