-
Notifications
You must be signed in to change notification settings - Fork 1.4k
✨ taint propagation: machine related API changes, conversion and feature gate #12936
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
✨ taint propagation: machine related API changes, conversion and feature gate #12936
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-conformance-main |
6a66d3b to
00f4464
Compare
|
/test pull-cluster-api-e2e-conformance-main |
1 similar comment
|
/test pull-cluster-api-e2e-conformance-main |
9f68423 to
aaecaf2
Compare
|
Rebased to resolve merge conflict (was on conversion due to #12940 ) |
|
/test pull-cluster-api-e2e-conformance-main |
aaecaf2 to
6b2c7e2
Compare
controlplane/kubeadm/internal/controllers/inplace_canupdatemachine_test.go
Outdated
Show resolved
Hide resolved
api/core/v1beta2/machine_types.go
Outdated
| // Only those taints defined in this list will be added or removed by core Cluster API controllers. | ||
| // | ||
| // NOTE: This list is implemented as a "map" type, meaning that individual elements can be managed by different owners. | ||
| // As of Kubernetes 1.33, this is different from the implementation on corev1.NodeSpec, but provides a more flexible API for components building on top of Cluster API. |
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 1.33 in this message? 1.34 also suffers the same issue
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.
Is this difference really something that anyone cares about and do we have to document it?
Cluster API supports co-ownership of this field and I don't see why we shouldn't be able to just do that even if the same is not possible on the corresponding Node field.
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.
Removed the second part of the note to simplify.
| // +listMapKey=key | ||
| // +listMapKey=effect | ||
| // +kubebuilder:validation:MinItems=1 | ||
| // +kubebuilder:validation:MaxItems=64 |
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.
Should explain the upper bound of this list length in the godoc
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.
Added:
// There can be at most 64 taints.
// A pod would have to tolerate all existing taints to run on the corresponding node.
Prior discussion: #12329 (comment)
fabriziopandini
left a comment
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.
Nice, just a few nits from my side
internal/controllers/machinedeployment/machinedeployment_rollout_planner.go
Show resolved
Hide resolved
2b066cb to
56b4da3
Compare
63fd146 to
de843f8
Compare
internal/controllers/machinedeployment/machinedeployment_controller_test.go
Outdated
Show resolved
Hide resolved
internal/controllers/machine/machine_controller_noderef_test.go
Outdated
Show resolved
Hide resolved
|
/test pull-cluster-api-e2e-main-gke |
internal/controllers/machine/machine_controller_noderef_test.go
Outdated
Show resolved
Hide resolved
|
One quick follow-up comment. Otherwise delta looks good. I'll do another full review a bit later in the week and give others some time to review as well in the meantime. |
|
Great work! |
|
LGTM label has been added. Git tree hash: 80b9a154866295ca494ed3c31948c9bb35465975
|
|
/retest Unrelated flake I think (MHC) |
|
/test pull-cluster-api-e2e-main-gke |
|
Thank you very much!! /lgtm |
|
LGTM label has been added. Git tree hash: f6b9a804180234b4f4b6ebd9345d4b64a1ad37b5
|
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: 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 |
|
/override pull-cluster-api-e2e-main-gke |
|
@sbueringer: Overrode contexts on behalf of sbueringer: pull-cluster-api-e2e-main-gke 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:
Part of:
Implements:
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 #
Area example:
/area api
/area machine
/area machineset
/area machinedeployment