creationTimestamp is null in all receipts

[corneliusweig]

All my receipts have such a header:

metadata:
   creationTimestamp: null
   name: krew

including creationTimestamp. This field carries no information and is annoying. There are two options:

• Get rid of this obsolete field.
• Fill the field when installing the plugin.

Following https://kubernetes.io/docs/reference/using-api/api-concepts/#generated-values, it seems most inline with k8s concepts, if the stored timestamp is the time when the plugin was first installed.

/help

[k8s-ci-robot]

@corneliusweig:
This request has been marked as needing help from a contributor.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

All my receipts have such a header:

metadata:
  creationTimestamp: null
  name: krew

including creationTimestamp. This field carries no information and is annoying. There are two options:

• Get rid of this obsolete field.
• Fill the field when installing the plugin.

Following https://kubernetes.io/docs/reference/using-api/api-concepts/#generated-values, it seems most inline with k8s concepts, if the stored timestamp is the time when the plugin was first installed.

/help

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/test-infra repository.

[ahmetb]

Agreed, let's add creationTimestamp: to the receipts to reflect installation date/time.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[chriskim06]

/remove-lifecycle stale

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

[chriskim06]

I'm planning on working on this soon.

/assign