Runners Controller 0.10.0 improves post-mortem debugging when a self-hosted runner disappears with a “lost communication” error. The controller now records the runner container’s exit code and reason before the terminal Pod is reaped, so the evidence survives in the controller logs instead of vanishing with the Pod.
- When a runner Pod reaches Succeeded or Failed, the controller logs the exit code, signal, and reason (for example,
137 OOMKilled,signal 15, or0 Completed) so you can quickly classify lost-communication failures from the controller logs.