-
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
🌱 Deprecate unused MachineDeployment constants #5241
Conversation
Do we have to deprecate the constants first and then drop them with v1beta1? |
Not sure in this case it seems they have never been exposed by us in any way so they should have never been able to be consumed in any way but may be I'm missing something. |
This is a breaking change, we should probably deprecate these first and remove them once we cut the next release |
b104496
to
2ae8f06
Compare
/retitle 🌱 Deprecate unused MachineDeployment constants |
2ae8f06
to
6d52909
Compare
controllers/mdutil/util.go
Outdated
@@ -44,17 +44,24 @@ const ( | |||
DefaultMachineDeploymentUniqueLabelKey = "machine-template-hash" | |||
|
|||
// FailedMSCreateReason is added in a machine deployment when it cannot create a new machine set. | |||
// Deprecated |
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.
// Deprecated | |
// Deprecated: This field will be removed in a next release. |
nit
Looks like we usually write either use another field/func or this will be removed.
Updated to deprecate them. Just to get full context this is technically breaking change but there's no way this can break anyone right? or am I missing something? |
This was first added here kubernetes-sigs#143 and it's never been used.
6d52909
to
ca7e71b
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.
/approve
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: vincepri 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 |
@enxebre They seem leftovers, it should be fine to remove them |
What this PR does / why we need it:
This was first added here #143 and it's never been used.
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 #