-
Notifications
You must be signed in to change notification settings - Fork 38.6k
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
Bug fix: Enable CRD field dropping for validation ratcheting #122329
Conversation
393589c
to
f676c99
Compare
/retest |
/lgtm |
LGTM label has been added. Git tree hash: df711fa0422d1eefc7de451ba7d652c668e64236
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jpbetz, 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 |
/priority critically-urgent |
@jpbetz: The label(s) 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. |
/triage accepted |
@jpbetz: The label(s) 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. |
/priority critical-urgent |
…29-origin-release-1.29 Automated cherry pick of #122329: Wire in field dropping for CRDs
/kind bug
/kind api-change
What this PR does / why we need it:
CRD field dropping was added to CRD validation ratcheting and carefully unit tested, but never got fully wired in.
Which issue(s) this PR fixes:
Special notes for your reviewer:
This should be cherry picked to 1.29 (#121034 was introduced in 1.29)
Does this PR introduce a user-facing change?