Events emitted by node-problem-detector sometimes omit the apiVersion field in the involvedObject of the event. This causes issues with downstream consumers, notably with kubectl events --for Node/<node-name>, which relies on the presence of involvedObject.apiVersion for filtering and does not display events that lack it.

See related issue in kubernetes/kubernetes: kubernetes/kubernetes#134490

Example of problematic event (does NOT show up with kubectl events --for ...):

kind: Event
count: 1074
eventTime: null
firstTimestamp: "2025-10-07T22:00:52Z"
involvedObject:
  kind: Node
  name: XXXXXXXXX
  uid: XXXXXXXXX
# apiVersion is missing
message: ...
reason: OOMKilling
source:
  component: kernel-monitor

Expected behavior:

• All events created by node-problem-detector should set involvedObject.apiVersion.

This will ensure events are visible to tools that use field selectors involving apiVersion, such as kubectl events --for ....