-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Closed as not planned
Labels
lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Description
I am following the example in https://book.kubebuilder.io/cronjob-tutorial/writing-tests.html, where it creates a Job with a status and calls client.Create. I'm doing similar with a third party CRD (tekton's PipelineRun) with a status subresource - however, in my testing, the status field isn't saved. The only way I can get it to save the status is first create the CRD, then retrieve the created CRD, and finally call client.Status().Update. Calling client.Status().Update on the initial struct I create doesn't work either (expected, I suppose, since it doesn't have a uuid?) - but no error is returned, so it seems like it worked.
In summary:
- Is
client.Createsupposed to update the status as well? - Should
client.Status().Updatereturn an error if it fails to update the status?
Metadata
Metadata
Assignees
Labels
lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.Denotes an issue or PR that has aged beyond stale and will be auto-closed.