ARC runners did not recover automatically after Github Outage
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 38/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- github-actions, go, helm, kubernetes
- 领域
- ci-cd, devops, infrastructure
调研方向
首先阅读 EphemeralRunnerReconciler 流程以及关联的 controller 和 runner 日志,重点关注注册失败和 GitHub 恢复后的 BrokerServer 退避。跟踪当前如何监控正在运行的 EphemeralRunners,以及如何观察注册是否有效。完成的标准是:检测到无效的 GitHub 注册,清理并重新配置受影响的 runner,并为恢复行为提供测试覆盖。
由索引模型根据 Issue 内容生成。
描述
Checks
- I've already read https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners-with-actions-runner-controller/troubleshooting-actions-runner-controller-errors and I'm sure my issue is not covered in the troubleshooting guide.
- I am using charts that are officially provided
Controller Version
0.13.1
Deployment Method
Helm
Checks
- This isn't a question or user support case (For Q&A and community support, go to Discussions).
- I've read the Changelog before submitting this issue and I'm sure it's not due to any recently-introduced backward-incompatible changes
To Reproduce
This is not reproducible directly as it is the byproduct of an incident.
see https://www.githubstatus.com/incidents/g9j4tmfqdd09
Describe the bug
During the GitHub Actions degraded availability incident on 2026-03-05 githubstatus.com/incidents/g9j4tmfqdd09), our ARC deployment experienced runners that became stuck in a bad state and were not automatically recovered after GitHub's services came back online.
These runners were registered before the incident, lost their registration during GitHub's degradation, and ARC never reconciled them back to a healthy state.
This was resolved by manually deleting all of the stuck ARC runner pods.
Describe the expected behavior
ARC has no garbage collection loop that reconciles GitHub-side runner registrations against actual Kubernetes pod state. The EphemeralRunnerReconciler only handles the forward path (create secret -> create pod -> monitor pod). It does not:
- Periodically verify that a runner's GitHub registration is still valid
- Detect runners whose registration was invalidated by a GitHub-side incident
- Clean up and re-provision runners that are running but no longer recognized by GitHub
I suggest that we should add periodic health check to the EphemeralRunnerReconciler that verifies the GitHub-side registration is still valid for running EphemeralRunners.
Additional Context
1. GitHub's `api.github.com/actions/runner-registration` endpoint became unavailable.
2. The ARC `EphemeralRunnerReconciler` failed to generate JIT configs for new runners, retrying 5 times with backoff before giving up.
3. Already-running runners lost their registrations on the GitHub side (`Registration <uuid> was not found`).
4. Runner pods entered `BrokerServer` backoff loops, unable to communicate with `broker.actions.githubusercontent.com`.
5. **After GitHub recovered at ~23:55 UTC, errors and backoff warnings continued until at least 00:17 UTC** — over 20 minutes of lingering failures. Runners that were mid-registration during the incident remained in a bad state with no automatic recovery.
Controller Logs
related logs:
https://gist.github.com/rob-howie-depop/27b15fd387ffc5f8f36e838614ffefc0
Runner Pod Logs
related logs:
https://gist.github.com/rob-howie-depop/27b15fd387ffc5f8f36e838614ffefc0
- 主要语言
- Go
- 星标
- 6.7k
- 派生
- 1.5k
- 平均合并
- 1 小时 34 分钟
- 30 天内合并 PR
- 5
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
actions/actions-runner-controller 的其他 Issue
-
community enhancement needs triage
难度 2/5 1-3 小时 新手友好度 68/100
actions/actions-runner-controller#3997 · 9 条评论 · 27 个 reaction ·
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 48/100
actions/actions-runner-controller#4739 · 1 条评论 · 4 个 reaction ·
维护者通常 1 天内回复
-
gha-runner-scale-set: support Google Cloud Secret Manager as a vault for GitHub credentials可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭community enhancement needs triage
难度 4/5 3-5 天 新手友好度 52/100
actions/actions-runner-controller#4737 · 1 条评论 ·
维护者通常 1 天内回复
-
Controller upgrade cancels jobs that started shortly before their runner set is deleted可能重新可做 @ankit373 于 9 天前认领,目前没有进行中的 PR。 未关闭
难度 4/5 3-5 天 新手友好度 45/100
actions/actions-runner-controller#4736 · 2 条评论 ·
维护者通常 1 天内回复
-
EphemeralRunnerSet controller creates more runners than `spec.replicas` when its cache lags its own creates可能已有人在做 @jia-pylon 于 14 天前认领。 未关闭
难度 4/5 3-5 天 新手友好度 30/100
actions/actions-runner-controller#4734 · 1 条评论 ·
维护者通常 1 天内回复
查看 actions/actions-runner-controller 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 82/100
-
needs discussion
难度 2/5 1-3 小时 新手友好度 78/100
openfga/openfga.dev#1436 · 1 条评论 ·
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 75/100
digital-go-jp/abr-geocoder#457 ·
维护者通常 3 天内回复
-
benchmark
难度 1/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 77/100
mozilla-ai/cq#601 ·
维护者通常 1 天内回复