-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
🌱 Implement Machine Deleting condition #11291
🌱 Implement Machine Deleting condition #11291
Conversation
6f8b05b
to
4936d2e
Compare
610d500
to
8bd926d
Compare
/test pull-cluster-api-e2e-main |
8bd926d
to
181d958
Compare
/test pull-cluster-api-e2e-main |
0629850
to
8e33e61
Compare
/test pull-cluster-api-e2e-main |
case deletingCondition.Reason == clusterv1.MachineDeletingDrainingNodeV1Beta2Reason && | ||
machine.Status.Deletion != nil && machine.Status.Deletion.NodeDrainStartTime != nil && | ||
time.Since(machine.Status.Deletion.NodeDrainStartTime.Time) > 30*time.Minute: | ||
msg = fmt.Sprintf("Machine deletion in progress, stage: %s (since more than 30m)", deletingCondition.Reason) |
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.
why is 30m a threshold? why don't we always print duration?
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.
The idea is to have a finite amount of messages, because the Ready conditions will be aggregated across all Machines of a MachineSet / MachineDeployment. If we use the exact duration the aggregation will never be able to de-duplicate messages from different Machines and the aggregated MachinesReady condition will be very verbose
I'll add a comment
/test pull-cluster-api-e2e-main |
Signed-off-by: Stefan Büringer [email protected]
Signed-off-by: Stefan Büringer [email protected]
3170c76
to
2973ede
Compare
Signed-off-by: Stefan Büringer [email protected]
2973ede
to
375bac1
Compare
/test pull-cluster-api-e2e-main |
Just one comment, otherwise lgtm :-) |
/lgtm |
LGTM label has been added. Git tree hash: 4e2462e819d050a33055a2cfabd30860a0b9d40d
|
@fabriziopandini @chrischdi @enxebre |
/test pull-cluster-api-e2e-main |
/lgtm |
LGTM label has been added. Git tree hash: 06874d23e56ed665229db087aaa6f7ae4ad21289
|
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: fabriziopandini 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:
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Part of #11105