The only controller change is #993, which tries to work-around the issue that your runner might be (unexpectedly) deleted even when it's still running a job. I wonder if it's a bug on GitHub Actions API but we need to deal with it so that users won't experience random job failures. See #911 for more information, and report any issues if you still see problems! Thank you.
What's Changed
- Add podDistruptionBudget resource for controller pods by @roeelandesman in #805
- chore: bumping chart for new release by @toast-gear in #948
- add
additionalVolumesandadditionalVolumeMountsto helm chart by @brunocous in #952 - fix: update volumes and volumes mounts indent by @gscho in #966
- ci: separate ubuntu versions out in ci by @toast-gear in #969
- chore(deps): bump 20.04 runner version by @toast-gear in #975
- docs: various clarifications by @toast-gear in #976
- ci: remove ubuntu 18.04 image by @toast-gear in #980
- docs: bring ephemeral runners to current by @toast-gear in #981
- chore(deps): update dependency actions/runner to v2.285.1 by @renovate in #985
- Support installing without cert-manager by @jsok in #834
- docs: remove RunnerSet limitation by @toast-gear in #991
- chore(deps): update quay.io/brancz/kube-rbac-proxy docker tag to v0.11.0 by @renovate in #745
- Workaround for offline+busy runners by @mumoshu in #993
New Contributors
- @roeelandesman made their first contribution in #805
- @brunocous made their first contribution in #952
- @gscho made their first contribution in #966
- @jsok made their first contribution in #834
Full Changelog: v0.20.3...v0.20.4