Skip to content

🐛 fake: set deletionTimestamp on object passed to Delete - #3558

Open
dpacgdm wants to merge 1 commit into
kubernetes-sigs:mainfrom
dpacgdm:fix/fake-client-delete-deletiontimestamp
Open

🐛 fake: set deletionTimestamp on object passed to Delete#3558
dpacgdm wants to merge 1 commit into
kubernetes-sigs:mainfrom
dpacgdm:fix/fake-client-delete-deletiontimestamp

Conversation

@dpacgdm

@dpacgdm dpacgdm commented Jul 21, 2026

Copy link
Copy Markdown

Summary

  • When fake Client.Delete soft-deletes an object because finalizers remain, copy deletionTimestamp onto the caller's object (same pattern as Create/Update/Get).
  • Add a unit test covering that behavior.
  • Adjust the existing finalizers-on-Patch test so MergeFrom preserves the timestamp now present on the deleted object.

This addresses the fake client half of #3059. The issue was later broadened to also cover the real typed client (.Error() vs .Into(obj)); that part is out of scope here and can land as a follow-up (see previously stalled #3098).

Test plan

  • go test ./pkg/client/fake/

When Delete soft-deletes due to finalizers, reflect deletionTimestamp
onto the caller's object like Create/Update/Get already do.
@kubernetes-prow
kubernetes-prow Bot requested review from JoelSpeed and inteon July 21, 2026 14:44
@kubernetes-prow

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: dpacgdm
Once this PR has been reviewed and has the lgtm label, please assign alvaroaleman for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@kubernetes-prow kubernetes-prow Bot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Jul 21, 2026
@kubernetes-prow

Copy link
Copy Markdown
Contributor

Welcome @dpacgdm!

It looks like this is your first PR to kubernetes-sigs/controller-runtime 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/controller-runtime has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

@kubernetes-prow

Copy link
Copy Markdown
Contributor

Hi @dpacgdm. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

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-sigs/prow repository.

@kubernetes-prow kubernetes-prow Bot added needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Jul 21, 2026

@alvaroaleman alvaroaleman left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/hold

Fake client should not do something the actual client doesn't do. We will have to make any change to this for the two in tandem. Its unclear if this is fixable because if the object is gone from storage, the apiserver doesn't return it in the response body

@kubernetes-prow kubernetes-prow Bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 22, 2026
@sbueringer

Copy link
Copy Markdown
Member

More context here: #3098

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants