Replies: 1 comment 4 replies
-
I think Kured can be configured to reboot on a schedule instead: https://kured.dev/docs/configuration/ |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
After using this module for some months now, I (finally) ran into this issue which I already expected from the beginning: As all new nodes use the static snapshot created when starting out, this snapshot becomes outdated over time.
With a working
kured
, new nodes spun up by the autoscaler will be checked bykured
. At some point,kured
will immediately apply updates. If these include a new kernel, it will also drain them and reboot.With the default config,
kured
will operate at any time and hence, the just freshly launched node (with 'fresh' being debatable due to the outdated snapshot) will be automatically drained and rebooted a few minutes after creation.This terminates the workload on the node, causing disruption for possible time-limited processes which were supposed to run and finish cleanly.
Possible Solutions
kured
24/7 by default but only at a time where nodes are infrequently spun up or no temporary workloads are processed (maybe 6 am?)Beta Was this translation helpful? Give feedback.
All reactions