-
Notifications
You must be signed in to change notification settings - Fork 1.4k
⚠️ Remove DefaulterRemoveUnknownOrOmitableFields mutating webhook option (again) #12404
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 DefaulterRemoveUnknownOrOmitableFields mutating webhook option (again) #12404
Conversation
/test pull-cluster-api-e2e-conformance-ci-latest-main |
010219e
to
f109de6
Compare
/approve /assign @sivchari |
[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 |
Thx! /lgtm |
LGTM label has been added. Git tree hash: c4497535825c2c8fc13db346371bb6c7f460ba9e
|
What this PR does / why we need it:
#12231 dropped DefaulterRemoveUnknownOrOmitableFields from all mutating web hook.
Before the alpha release, #12290 partially reverted this change because we were observing issue in KCP.
Now, after triaging the issue in KCP, and opened #12402 to fix it, we can finally drop DefaulterRemoveUnknownOrOmitableFields mutating webhook option (again).
Additionally, this PR adds a unit test that proves that dropping DefaulterRemoveUnknownOrOmitableFields do not lead to rollouts or infinite reconciles in the topology controller.
However, in case you have patches generating omitable fields like e.g. an empty string, or an empty array, this might lead to rollouts when you rebase to a cluster class using v1beta2 references (or you change a cluster class in place, which is not recommended).
/area clusterclass
Part of #10852