Actions Runner Controller release 0.15.0
GitHub Actions Runner Controller 0.15.0 includes reliability, scalability, and observability improvements for runner scale sets.
By Dillip Chowdary • Oct 01, 2026 • Source: GitHub Changelog
What Actions Runner Controller shipped
Back to changelog GitHub Actions Runner Controller 0.15.0 includes reliability, scalability, and observability improvements for runner scale sets. These updates help you operate larger runner fleets with fewer disruptions during upgrades and Kubernetes API updates.
Here’s what’s now available: Patch version upgrades now update resources in place, reducing disruption between autoscaling runner sets and ephemeral runner sets. Controller shutdown behavior is more reliable because terminationGracePeriodSeconds is configurable and now aligns with the controller manager graceful shutdown timeout.
What changed for builders in Actions Runner Controller

Runner scale sets can be reregistered when the recorded scale set no longer exists in the Actions service. See the full write-up from GitHub Changelog via the source link for quotes and complete context.
Advertisement
Tech Pulse Daily
Get tomorrow's pulse first
Join engineers who read Tech Pulse before stand-up. Free, weekday mornings.
How to install or upgrade Actions Runner Controller
Controller updates now use patch requests instead of full update requests, reducing Kubernetes API payload size. Runner status aggregation has moved to metrics for EphemeralRunnerSet and AutoscalingRunnerSet, reducing status patch requests.
Gotchas and compatibility in Actions Runner Controller
Listener Kubernetes client rate limits are configurable through QPS and burst settings. Controller concurrency can now be configured globally and per controller with max-concurrent-reconciles flags.
What to watch after Actions Runner Controller
Controllers now filter incoming events so they perform fewer reconciliations than before. See the full write-up from GitHub Changelog via the source link for quotes and complete context.
Developer Action Items
- ☐ Diff the official changelog for GitHub / Kubernetes 0.15.0 before you bump — APIs, defaults, and removed flags only.
- ☐ Install through the vendor's documented channel in staging; keep a one-command rollback and time-box the canary.
- ☐ Grep your repo for old flag names, lockfile pins, and plugin versions that the notes mark as breaking.
- ☐ Prefer the first patch cut over the day-zero tag unless you have a reason to be on the leading edge.
- ☐ If GitHub Changelog did not name a region, plan, or SKU, screenshot the official availability line before you promise it to users.
Author
Dillip Chowdary
Writes Tech Bytes coverage of AI, engineering, and the tools that actually ship. Editor of Tech Pulse Daily.
Related on Tech Bytes
‘HomePad’ could launch in these four colors, per leaker
Read →
Announcing Ranveer Singh as Brand Ambassador for Ray-Ban and Ray-Ban Meta in India along…
Read →
Qualcomm Unveils Linux Preview on Snapdragon X2 to Accelerate Upstream ARM Laptops
Read →
Kiteworks patches max severity code injection vulnerability
Read →
Today's Tech Pulse briefing
Full briefing →
Advertisement