-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
🐛 Update object upon deletion #3098
base: main
Are you sure you want to change the base?
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: bigkevmcd The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Hi @bigkevmcd. 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 Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
/ok-to-test |
e2ca8b7
to
68cdf84
Compare
899f3e3
to
8ed5e0b
Compare
If an object is deleted and the API responds with a resource, update the deleted object. This causes the object to be updated with the deletion timestamp. Signed-off-by: Kevin McDermott <[email protected]>
8ed5e0b
to
5b4fcfc
Compare
/ok-to-test |
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.
Thanks, this is great! We also need to update the fake client to match the behavior
nodeName := node.Name | ||
err = cl.Delete(context.TODO(), node) | ||
Expect(err).NotTo(HaveOccurred()) | ||
Expect(node.ObjectMeta.DeletionTimestamp).NotTo(BeNil()) |
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.
Can we also test this with unstructured.Unstructured
and metav1.MetaObject
, please?
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.
Unstructured works... metav1.MetaObject will require a fair bit more work.
return resInt.Delete(ctx, metadata.Name, *deleteOpts.AsDeleteOptions()) |
Not sure if this is relevant?
// TODO(directxman12): we could rewrite this on top of the low-level REST |
Signed-off-by: Kevin McDermott <[email protected]>
My reading of this test is that the fake client does actually work?
|
That example is after a |
/assign |
If an object is deleted and the API responds with a resource, update the deleted object.
This causes the object to be updated with the deletion timestamp.
The fake Client was already behaving like this.