-
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
⚠️ Remove unused MachinePool deployment strategy #3990
⚠️ Remove unused MachinePool deployment strategy #3990
Conversation
@CecileRobertMichon: GitHub didn't allow me to request PR reviews from the following users: shysank. Note that only kubernetes-sigs members and repo collaborators can review this PR, and authors cannot review their own PRs. 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/test-infra repository. |
/lgtm |
/milestone v0.4.0 |
/cc @mytunguyen |
a8fecff
to
ad87315
Compare
ad87315
to
207aadd
Compare
@CecileRobertMichon: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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. I understand the commands that are listed here. |
/lgtm |
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 |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: detiber 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: MachinePool spec has MachineDeploymentStrategy which is unused. We don't know if all machine pool implementors will be able to replicate the behavior of MachineDeployment. Also, any changes made to MachineDeploymentStrategy spec will also alter the spec of machine pool, and we don't want that. For now, this removes deployment strategy from the MachinePool spec. We might consider adding a MachinePool specific deployment strategy later on if there is a contract between providers to support certain strategies.
This is technically a breaking change so marking it as so but the Strategy was never used so this won't change any behavior (and MachinePools are still in exp).
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 #3813