v1.470.0
cloudposse-releaser
released this
08 Jul 16:07
·
104 commits
to refs/heads/main
since this release
[eks/actions-runner-controller] Multiple bug fixes and enhancements @Nuru (#1075)
what
New Features:
- Add support for scheduled overrides of Runner Autoscaler min and max replicas.
- Add option
tmpfs_enabled
to have runners use RAM-backed ephemeral storage (tmpfs
,emptyDir.medium: Memory
) instead of disk-backed storage. - Add
wait_for_docker_seconds
to allow configuration of the time to wait for the Docker daemon to be ready before starting the runner. - Enhance the ability to have the runner Pods add annotations to themselves once they start running a job.
Changes:
- Previously,
syncPeriod
, which sets the period in which the controller reconciles the desired runners count, was set to 120 seconds inresources/values.yaml
. This setting has been removed, reverting to the default value of 1 minute. You can still set this value by setting thesyncPeriod
value in thevalues.yaml
file or by settingsyncPeriod
invar.chart_values
. - Previously,
RUNNER_GRACEFUL_STOP_TIMEOUT
was hardcoded to 90 seconds. That has been reduced to 80 seconds. - The inaccurately named
webhook_startup_timeout
has been replaced withmax_duration
.webhook_startup_timeout
is still supported for backward compatibility, but is deprecated.
Bugfixes:
- Create and deploy the webhook secret when an existing secret is not supplied
- Restore proper order of operations in creating resources (broken in release 1.454.0 (PR #1055))
- If
docker_storage
is set anddockerdWithinRunnerContainer
istrue
(which is hardcoded to be the case), properly mount the docker storage volume into the runner container rather than the (non-existent) docker sidecar container.
why
New Features:
- Enable having idle runners during work hours without having to pay for them during non-work hours.
- Enable packing more Runners onto an instance without being constrained by disk I/O.
- Allow for extended disk I/O waits when some Runner gets greedy.
- Intended to make idle Runners interruptible and running runners uninterruptible under Karpenter, but it does not work well enough for that. Still, we implemented the feature, so we might as well leave it in. Adds logging to help diagnose race conditions.
Changes:
- More responsive scaling
- Increases the chances the runner will successfully deregister itself
- The old name was extremely confusing, while the new name is much more reflective of its impact
Bugfixes:
- Restore intended operation
references
[eks/karpenter] Add support for `kubelet` config, fix IAM support for `v1alpha` cleanup @Nuru (#1076)
what
- Support configuration of
spec.template.spec.kubelet
- Fix issues with IAM Policy supporting management of v1alpha resources
why
- Default reservations for system resources under Amazon Linux are often inadequate and benefit from being able to be tuned
- Previous policy had errors, and would become too long if the cluster name got too long