Releases: actions/actions-runner-controller
actions-runner-controller-0.12.0
CAUTION: Beware to review changes to CRDs and do manually upgrade CRDs! Helm installs CRDs only on installing a chart. It doesn't automatically upgrade CRDs. Otherwise you end up with troubles like #427, #467, and #468. Please refer to the UPGRADING docs for the latest process.
See https://github.com/actions-runner-controller/actions-runner-controller/releases/tag/v0.19.0 for the new features that are not Helm specific.
Helm changes in this release:
- @yfried made the kube-proxy optional for the Helm chart (#511 #527)
- @Natanande added topologySpreadConstraints to helm chart (#569)
- @cdobinsky added pod labels to helm chart (#583
actions-runner-controller-0.11.0
A Kubernetes controller that operates self-hosted runners for GitHub Actions on your Kubernetes cluster.
actions-runner-controller-0.10.5
A Kubernetes controller that operates self-hosted runners for GitHub Actions on your Kubernetes cluster.
v0.18.2: Fix critical regression in v0.18.1
CAUTION: If you're using the Helm chart, beware to review changes to CRDs and do manually upgrade CRDs! Helm installs CRDs only on installing a chart. It doesn't automatically upgrade CRDs. Otherwise you end up with troubles like #427, #467, and #468
This release includes the following changes from contributors. Thank you!
v0.18.1: Fix dindWithinRunnerContainer, easier docker MTU configuration, support for runner group names and labels that contain spaces
CAUTION: If you're using the Helm chart, beware to review changes to CRDs and do manually upgrade CRDs! Helm installs CRDs only on installing a chart. It doesn't automatically upgrade CRDs. Otherwise you end up with troubles like #427, #467, and #468
This release includes the following changes from contributors. Thank you!
- @mumoshu fixed
dindWithinRunnerContainer: true
not to crash-loop runner pods (#419) - @gabriel-dantas98 fixed some readme typos (#423)
- @mumoshu Fixed MTU configuration for dockerd (#421)
- @FloThinksPi added proper quoting of shell vars in runner's
entrypoint.sh
to prevent unwanted argument split (#420)- Runner group names and runner labels that contain spaces is now valid and should just work
v0.18.0: Optional "Webhook-based Autoscaling" to go beyond GitHub API rate limit, and various usability, reliability, and observability enhancements
CAUTION: If you're using the Helm chart, beware to review changes to CRDs and do manually upgrade CRDs! Helm installs CRDs only on installing a chart. It doesn't automatically upgrade CRDs. Otherwise you end up with troubles like #427, #467, and #468
This release includes the following changes from contributors. Thank you!
- Webhook-based autoscaling to go beyond GitHub API rate limit (#282, follow-ups #363, #381, #386, #390, #391, #395, #398, #404, $406, #407)
- Documentation available at https://github.com/summerwind/actions-runner-controller#faster-autoscaling-with-github-webhook
- Also thanks to @robwhitby for implementing the loadbalancer healthcheck endpoint (#378)
- @alex-mozejko has fixed the entrypoint script to gracefully handle self-updates (#284)
- TotalNumberOfQueuedAndInProgressWorkflowRuns has been fixed to support large-scale deployment (#295)
- actions-runner-controller is now able to automatically retry registration timeouts (#297, and #309 by @jonico)
- @jonico enhanced the controller to gracefully handle crashed nodes and stuck runner pods (#307)
- You can now add common runner labels per controller for e.g. easy "environment" labeling (#327)
- Runner registration check if now more reliable and has smaller chance of being rate limited by GitHub API (#405)
- @jonico fixed setting the runner group for enterprise runners (#376)
- actions-runner-controller is now able to restrict itself to a single namespace. This gives more chances to scale (#380, also #377 for related discussion and experience managing 100+ runners with actions-runer-controller)
- @tapih enhanced the controller support two or more RunnerDeployments in a namespace (#355, follow-up #386, #371)
- Rolling-update on RunnerDeployment has much smaller chance of disrupting progressing workflow jobs (#392)
- Various controller is now reliable- It has smaller chances of conflicts because it's updated to use Patch instead of Update whereas possible
- @int128 added metrics useful for observing the number of runners (#408)
- Runner controller is now part of our integration test suite. It should make subsequent releases more reliable (#409)
- Documentation has been greatly enhanced thanks to @callum-tait-pbx, and received various fixes from @mikeperry-kr, @ba32107, @robwhitby! (enhancements #303, #359 and #379, fixes #370, #373, #394, )
- Controller logs are now easier to read (#311 by @jonico, #410)
actions-runner-controller
is now listed in awesome-runners 🎉
actions-runner-controller-0.10.4
A Kubernetes controller that operates self-hosted runners for GitHub Actions on your Kubernetes cluster.
actions-runner-controller-0.10.3
A Kubernetes controller that operates self-hosted runners for GitHub Actions on your Kubernetes cluster.
actions-runner-controller-0.10.2
A Kubernetes controller that operates self-hosted runners for GitHub Actions on your Kubernetes cluster.
actions-runner-controller-0.10.1
A Kubernetes controller that operates self-hosted runners for GitHub Actions on your Kubernetes cluster.