-
Notifications
You must be signed in to change notification settings - Fork 39.8k
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
Revert v1beta1 PodDisruptionBudget selector patchStrategy to pre-1.21 behavior #108138
Conversation
@liggitt: This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the The 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. |
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.
Thank you for the quick turnaround on this!
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: 2rs2ts, liggitt 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 |
added an integration test exercising all strategic merge patch, merge patch, and apply patch types against v1 and v1beta1. Verified the test passes against this PR, passes against release-1.20 (with the v1 cases skipped, since the v1 API didn't exist then), and fails against release-1.21, release-1.22, release-1.23, and master. |
/retest |
This PR may require API review. If so, when the changes are ready, complete the pre-review checklist and request an API review. Status of requested reviews is tracked in the API Review project. |
/lgtm Huge thanks for fixing. |
Will this be backported to 1.21-23? |
yes, cherry-picks already open and linked |
…138-upstream-release-1.21 Automated cherry pick of #108138: Revert v1beta1 PodDisruptionBudget select patchStrategy
…138-upstream-release-1.22 Automated cherry pick of #108138: Revert v1beta1 PodDisruptionBudget select patchStrategy
…138-upstream-release-1.23 Automated cherry pick of #108138: Revert v1beta1 PodDisruptionBudget select patchStrategy
What type of PR is this?
/kind bug
/kind regression
What this PR does / why we need it:
Reverts strategic merge patch behavior for the
selector
field inv1beta1
PodDisruptionBudget objects to match pre-1.21 behavior.Which issue(s) this PR fixes:
Fixes #108137
Does this PR introduce a user-facing change?
/cc @mortent
/cc @jpbetz