Exporter should buffer events/conditions until node is ready #1079
Description
when NPD is running in standalone mode, it attempts to export Events and patch node Conditions immediately upon starting. During initial node bootstrap, the kube-apiserver may not be reachable, or the kubelet may not have fully registered the node yet.
In this scenario, the NPD exporter's calls will fail, and the initial events or critical readiness conditions are lost. This race condition could be addressed by buffering the node events/conditions until the node is fully integrated with the control plane. Once npd verifies the node object exists, it should flush the buffer, and submit all the queued events and condition patches. This would make npd k8s exporter more reliable.