-
Notifications
You must be signed in to change notification settings - Fork 42k
fieldmanager: Strip managedfields BEFORE we update the timestamp #100032
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
fieldmanager: Strip managedfields BEFORE we update the timestamp #100032
Conversation
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: apelisse The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
Actually that one only updates the time on update. Still thinks this is best. |
|
/triage accepted |
|
/assign @jpbetz |
|
/retest |
|
/wg api-expression |
|
/lgtm |
|
You might also want to do it here: kubernetes/staging/src/k8s.io/apiserver/pkg/endpoints/handlers/fieldmanager/fieldmanager_test.go Line 114 in 4740173
|
|
/lgtm Makes perfect sense to me that to detect a noop change, any fields stripping needs to happen first |
I don't know why I said that, it absolutely works for apply too! |
1b8f227 to
c8be965
Compare
|
the test was already doing the right thing (building the managers in the right order). I've added a "creationTimestamp" to show that this works. |
|
/lgtm |
|
/retest Review the full test history for this PR. Silence the bot with an |
What type of PR is this?
/kind bug
What this PR does / why we need it:
Which issue(s) this PR fixes:
Discovered by #100024
Special notes for your reviewer:
Does this PR introduce a user-facing change?