Johannes Nicolai 2d7fbbfb68 Handle offline runners gracefully (#341) ...

* if a runner pod starts up with an invalid token, it will go in an 
infinite retry loop, appearing as RUNNING from the outside
* normally, this error situation is detected because no corresponding 
runner objects exists in GitHub and the pod will get removed after 
registration timeout
* if the GitHub runner object already existed before - e.g. because a 
finalizer was not properly run as part of a partial Kubernetes crash, 
the runner will always stay in a running mode, even updating the 
registration token will not kill the problematic pod
* introducing RunnerOffline exception that can be handled in runner 
controller and replicaset controller
* as runners are offline when a pod is completed and marked for restart, 
only do additional restart checks if no restart was already decided, 
making code a bit cleaner and saving GitHub API calls after each job 
completion

2021-02-22 10:08:04 +09:00

..

fake

Fix TotalNumberOfQueuedAndInProgressWorkflowRuns to work with a lot of remaining completed jobs (#316)

2021-02-16 18:55:55 +09:00

metrics

Add metrics for GitHub API rate limit (#312)

2021-02-16 09:58:09 +09:00

github_test.go

feat: HorizontalRunnerAutoscaler Webhook server (#282)

2021-02-07 17:37:27 +09:00

github.go

Handle offline runners gracefully (#341)

2021-02-22 10:08:04 +09:00