Ryan Phillips 5d3c07e89d kubelet: only emit one reboot event ...

There are cases when the kubelet is starting where networking, or other
components can cause the kubelet to not post the status with the bootId.
The failed status update will cause the Kubelet to queue the
NodeRebooted warning and sometimes cause many events to be created.

This fix wraps the recordEventFunc to only emit one message per kubelet
instantiation.

2024-12-10 16:44:17 -06:00

..

setters_test.go

add more testing for node.status.addresses

2024-06-16 16:07:52 +00:00

setters.go

kubelet: only emit one reboot event

2024-12-10 16:44:17 -06:00