Skip to content

do not always undrain node#2113

Merged
itechdima merged 1 commit intosoperator-release-2.0from
SCHED-869/do-not-always-undrain-node
Feb 2, 2026
Merged

do not always undrain node#2113
itechdima merged 1 commit intosoperator-release-2.0from
SCHED-869/do-not-always-undrain-node

Conversation

@itechdima
Copy link
Collaborator

@itechdima itechdima commented Jan 30, 2026

Problem

K8S nodes are always undrained by our nodeconfigurator. So in case of k8s needs to replace node softly with drain, our configurator interferes in that flow and doesn't allow it. Also, there's a race with node restarts, so instead of restarting one time it could go several times in a row.

Solution

  • Undrain nodes only in case it was our restart
  • Fix race that leads to several restarts in a row

Testing

Dev cluster

Release Notes

Fix: race during node restart process. Now nodes are restarted only once.
Fix: nodeconfigurator undrains k8s nodes only after restart and once.

@itechdima itechdima added the fix label Jan 30, 2026
@itechdima itechdima force-pushed the SCHED-869/do-not-always-undrain-node branch 2 times, most recently from b8179db to 394302f Compare February 2, 2026 12:48
@itechdima itechdima force-pushed the SCHED-869/do-not-always-undrain-node branch from 394302f to fc4fbca Compare February 2, 2026 14:24
@itechdima itechdima marked this pull request as ready for review February 2, 2026 16:22
@itechdima itechdima merged commit 841ca25 into soperator-release-2.0 Feb 2, 2026
10 checks passed
@itechdima itechdima deleted the SCHED-869/do-not-always-undrain-node branch February 2, 2026 16:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants