-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
✨ Update machineset with v1beta2 status test #11278
Conversation
/test help |
@chrischdi: The specified target(s) for
The following commands are available to trigger optional jobs:
Use
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. |
/test pull-cluster-api-e2e-main |
d8cd89f
to
6129e87
Compare
6129e87
to
e8980ec
Compare
e8980ec
to
417a033
Compare
0a0a965
to
e863569
Compare
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.
Great work!
just nits and small improvements, nothing really blocking
internal/controllers/machineset/machineset_controller_status.go
Outdated
Show resolved
Hide resolved
internal/controllers/machineset/machineset_controller_status.go
Outdated
Show resolved
Hide resolved
internal/controllers/machineset/machineset_controller_status.go
Outdated
Show resolved
Hide resolved
internal/controllers/machineset/machineset_controller_status.go
Outdated
Show resolved
Hide resolved
internal/controllers/machineset/machineset_controller_status.go
Outdated
Show resolved
Hide resolved
internal/controllers/machineset/machineset_controller_status.go
Outdated
Show resolved
Hide resolved
internal/controllers/machineset/machineset_controller_status.go
Outdated
Show resolved
Hide resolved
internal/controllers/machineset/machineset_controller_status.go
Outdated
Show resolved
Hide resolved
// TODO Deleting | ||
} | ||
|
||
func setReplicas(ms *clusterv1.MachineSet, machines []*clusterv1.Machine) { |
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.
nit: let's pass the context into all those func, so it is already there in case we should log
internal/controllers/machineset/machineset_controller_status.go
Outdated
Show resolved
Hide resolved
internal/controllers/machineset/machineset_controller_status.go
Outdated
Show resolved
Hide resolved
internal/controllers/machineset/machineset_controller_status.go
Outdated
Show resolved
Hide resolved
internal/controllers/machineset/machineset_controller_status.go
Outdated
Show resolved
Hide resolved
c611ea6
to
4502600
Compare
internal/controllers/machineset/machineset_controller_status.go
Outdated
Show resolved
Hide resolved
3e6d2c3
to
a7e1481
Compare
internal/controllers/machineset/machineset_controller_status.go
Outdated
Show resolved
Hide resolved
Type: clusterv1.MachineSetMachinesReadyV1Beta2Condition, | ||
Status: metav1.ConditionFalse, | ||
Reason: v1beta2conditions.MultipleIssuesReportedReason, | ||
Message: "Deleting: Machine deletion in progress, stage: DrainingNode from Machine machine-4; HealthCheckSucceeded: Some message from Machine machine-2; Some unknown message from Machine machine-3", |
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.
@fabriziopandini Not for this PR, but in general this is hard to parse. A listing like we have in Node drain would make this a lot easier
internal/controllers/machineset/machineset_controller_status_test.go
Outdated
Show resolved
Hide resolved
Very nice work!! /lgtm /hold |
LGTM label has been added. Git tree hash: aebafa1427a50bfbbb79708676e9f063fd6a14b8
|
/test pull-cluster-api-e2e-main |
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
/approve
Great job!
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: fabriziopandini, sbueringer 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 |
/hold cancel |
/override pull-cluster-api-e2e-main |
@sbueringer: Overrode contexts on behalf of sbueringer: pull-cluster-api-e2e-main 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. |
What this PR does / why we need it:
This PR adds code for updating machine with v1beta2 status.
In order to do so, reconcile bootstrap config, infrastructure and getAndAdoptMachines will now always run, ensuring info from those resources are always surfaced.
Also fixes the status information on deletion, which was stale during deletion and with foreground deletion enabled.
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 #
xref:
/area api