`involvedObjet.apiVersion` is missing from node events. This prevents console from showing node as the type (since it relies on `apiVersion` and `kind` to add a resource link). Version: 4.5.0-0.ci-2020-02-29-231846 Here's an event with the problem: - apiVersion: v1 count: 1 eventTime: null firstTimestamp: "2020-03-01T14:20:08Z" involvedObject: kind: Node name: ip-10-0-132-152.us-east-2.compute.internal uid: ip-10-0-132-152.us-east-2.compute.internal kind: Event lastTimestamp: "2020-03-01T14:20:08Z" message: Starting kubelet. metadata: creationTimestamp: "2020-03-01T14:20:08Z" name: ip-10-0-132-152.us-east-2.compute.internal.15f833f7e31baf6d namespace: default resourceVersion: "1974" selfLink: /api/v1/namespaces/default/events/ip-10-0-132-152.us-east-2.compute.internal.15f833f7e31baf6d uid: 803a3c58-c41a-4af7-b07a-09a239084219 reason: Starting reportingComponent: "" reportingInstance: "" source: component: kubelet host: ip-10-0-132-152.us-east-2.compute.internal type: Normal
A node object is internal and lacks a version number, so I believe this is expected behavior.
Found an issue and PR: https://github.com/kubernetes/kubernetes/pull/87537 https://github.com/kubernetes/kubernetes/issues/87506
Sam: After talking to David, would you like me to pick the patch, or would you like to code around it? Patch is approved.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (OpenShift Container Platform 4.5 image release advisory), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:2409