-
Notifications
You must be signed in to change notification settings - Fork 1.4k
✨ MachinePools: Use NodeDeletionTimeout and default it to 10s #10553
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
Conversation
Welcome @serngawy! |
Hi @serngawy. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
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.
/ok-to-test
/area machinepools
@killianmuldoon: The label(s) In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
I think this one goes into a different direction then described in: and /hold |
/cc @mboersma |
@mboersma would review the PR and let me know your thoughts. |
022d53e
to
6da8906
Compare
I think we're almost there :) |
@serngawy If you got time, if we get the findings addressed pretty soon, we'll get this merged in time for v1.8 :) (just a heads up) (Feel free to ping me in Slack for another review) |
Thanks @sbueringer for the follow up. Unfortunately in PTO this week, will work on it next week. |
Enjoy your time off! |
3ad8d1b
to
90431ac
Compare
Please rebase this PR on top of main instead of merging main into this PR. I don't remember the exact reason, but I think we run into problems when we merge PRs that have merge commits from main |
Let's rebase onto main, address #10553 (comment) and then merge this PR I'll probably do another iteration on the unit tests as a follow-up PR. I would prefer testing slightly more realistic scenarios |
Signed-off-by: melserngawy <[email protected]>
Thank you! /lgtm /assign @chrischdi |
LGTM label has been added. Git tree hash: 1743c72d9a5ea8b6c72eb26bfb742cb09deecddf
|
/retest |
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 we change the title to something which better describes this change?
I think this currently not only makes "MachinePools to honour the NodeDeletionTimeout".
Am I right that this also helps deleting a MachinePool when Bootstrap.ConfigRef
or InfrastructureRef
is not set?
If yes the title should highlight both because it will be part of release notes (ok to have as follow-up).
if m.Spec.Template.Spec.NodeDeletionTimeout == nil { | ||
m.Spec.Template.Spec.NodeDeletionTimeout = &metav1.Duration{Duration: defaultNodeDeletionTimeout} | ||
} |
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.
Adding defaulting to 10 seconds and skipping the node deletion IMHO is a change in the behaviour of the controller.
Should we mark this as feature (❇️ ) in the title?
Note: this should not get cherry-picked to older release branches, but maybe folks more involved in MachinePools can argue better.
/retitle ✨ MachinePools: Use NodeDeletionTimeout and default it to 10s /approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: chrischdi The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What this PR does / why we need it:
Ignore unreachable cluster while deleting machinePools
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #10544