Job/Pipeline logic to correctly handle temporary loss of gitlab runner orchestrator
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Problem to solve
If the gitlab runner orchestrator goes offline during a GitLab stage pod run, the GitLab stage pod should continue to execute and complete (as another GitLab runner orchestrator will come online), however, the GitLab stage pod may become orphaned and will never shut down, as the original GitLab runner orchestrator is not available. The GitLab UI may also never catchup, and the stage may look like this forever:
Proposal
Add failure logic which would run when a GitLab runner orchestrator starts to check for any running but orphaned jobs.
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.