-
Notifications
You must be signed in to change notification settings - Fork 210
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: add drain delay #852
Conversation
any idea why the E2E for 1.27 is failing? is it a transient problem - can we retry the job? |
Sometimes single test-run's are failing. This is unrelated to your changes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you please open additional PRs to the website and chart-repo?
Thanks for the addition!!
I've opened two additional PR to add the flag to the configuration properties and parameter docs. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
Signed-off-by: Daniel Malon <[email protected]>
14d2bcd
to
2c1be3c
Compare
@MerlinDMC FYI I rebased on top of main and force-pushed to attempt to overcome unexplained E2E errors. Will merge when we get a green signal. |
This PR adds a
--drain-delay
flag.The duration given will delay the node draining process to allow for other controllers in the cluster to complete work.
We are using
--pre-reboot-node-labels=node.kubernetes.io/exclude-from-external-load-balancers=true
to signal the load balancer controller to start draining connections from the node as it is about to be drained.With the flag added we can delay the draining process to ensure the load balancer controller has enough time to remove the node from active traffic flow before the draining starts.