You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
test: verify upgrade drain honors grace period and aborts on failure
Before Talos 1.13 the drain happened inside machined as part of the upgrade sequence. It evicted every pod with a hardcoded 60 second grace period, and it logged eviction failures instead of returning them, so the node rebooted whether or not the workload had actually finished shutting down.
Omni now runs the drain itself for cluster on 1.13 and up, passing each pod's own terminationGracePeriodSeconds through and refusing to reboot when the drain does not complete.
Nothing covered that end to end. The new suite parks a two-replica workload behind a PodDisruptionBudget, has it ignore SIGTERM for six minutes, then upgrades the cluster and rebuilds the drain timeline by sampling pod, node and ClusterMachineConfigStatus state. It checks that the eviction carried the pod's full grace period rather than a fixed one, that the drain failure surfaced instead of being swallowed, and that the node's boot ID only changed once the pod was gone.
Signed-off-by: Oguz Kilcan <oguz.kilcan@siderolabs.com>
0 commit comments