kubectl: fix the Scheduled eventTime is <unknown> when printing event

[gosoon]

What type of PR is this?
/kind bug

What this PR does / why we need it:
When scheduler using v1beta1.events(#78447),the Scheduled event is not set the LastTimestamp and the FirstTimestamp,only set the EventTime,so use kubectl get event and kubectl describe pod xxx you will see that the timestamp of the scheduled event is <unknown>,as shown below,in those cases we fallback to eventTime.

$ kubectl get event
LAST SEEN   TYPE     REASON              OBJECT                        MESSAGE
<unknown>   Normal   Scheduled           pod/nginx-6c975b59f8-gvmjr    Successfully assigned default/nginx-6c975b59f8-gvmjr to minikube

$ kubectl describe pod xxx
......
Events:
  Type    Reason     Age        From               Message
  ----    ------     ----       ----               -------
  Normal  Scheduled  <unknown>  default-scheduler  Successfully assigned default/nginx-6c975b59f8-gvmjr to minikube
......

Which issue(s) this PR fixes:

Fixes # 89689

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

Fix kubectl printer to correctly handle timestamps of events emitted using events.k8s.io API

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

None

[k8s-ci-robot]

Hi @gosoon. Thanks for your PR.

I'm waiting for a kubernetes 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.

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.

[gosoon]

/sig cli

[gosoon]

/area kubectl

[zhouya0]

Thanks for your PR, but seems this is dup of #89999 which is still waiting for another review.
Maybe you could add kubectl describe part after that PR is merged.

[gosoon]

Ok, I have changed the commit content and only fixed the kubectl describe pod xxx part.

[zhouya0]

EventTime is metav1.MicroTime but not metav1.Time. So you need another translateMicroTimestampSince . Like #89999

[gosoon]

done

[zhouya0]

/ok-to-test
/lgtm

[soltysh]

/approve
/priority backlog
/retest

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: gosoon, soltysh

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

The pull request process is described here

Needs approval from an approver in each of these files:

• staging/src/k8s.io/kubectl/OWNERS [soltysh]

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

[dmcnaught]

We're seeing this issue in one of our 1.16.8 clusters. Can we get the fix added to a 1.16 point release?

[dmcnaught]

@gosoon We're having this problem with one of our 1.16 clusters and are wondering when/if there will be a 1.16 patch release to fix it. Do you know?

[cpanato]

@dmcnaught Hello Duncan, 1.16 is no longer receiving the patch releases, I recommend you to upgrade your cluster to 1.17 at least.
The current supported Kubernetes versions are 1.17 / 1.18 and 1.19

[dmcnaught]

@dmcnaught Hello Duncan, 1.16 is no longer receiving the patch releases, I recommend you to upgrade your cluster to 1.17 at least.
The current supported Kubernetes versions are 1.17 / 1.18 and 1.19

yes - we upgraded to 1.17 in July/August.

There was a PR in our PaaS that helps up around the unknown timestamps: teamhephy/controller#129