<p>I am trying to understand the Node-Controller in Kubernetes. Kubernetes <a href="https://kubernetes.io/docs/concepts/architecture/nodes/#heartbeats" rel="nofollow noreferrer">documentation</a> mentions that node heartbeats are done using NodeStatus and LeaseObject updates. Someone, please explain why both mechanisms are needed for monitoring node health.
Does Kubernetes master internally use a job/cronjob for a node health check processing?</p>

<p><a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#lease-v1-coordination-k8s-io" rel="nofollow noreferrer">Lease</a> is a lightweight resource, which improves the performance of the node heartbeats as the cluster scales.</p>
<p>The Lease objects are tracked as a way of helping the heartbeats to continue functioning efficiently as a cluster scales up. According to the docs, this would be their primary function relating to heartbeats.</p>
<p>Whereas the <code>NodeStatus</code> is used for Heartbeats by the kubelet, <code>NodeStatus</code> is also an important signal for other controllers in k8s.</p>
<p>For example: the k8s scheduler is responsible for scheduling pods on nodes. It tries to find the best fit for a node to optimize memory, cpu, and other usage on the node. It wouldn't however want to schedule a pod on a node with <a href="https://kubernetes.io/docs/concepts/architecture/nodes/#node-status" rel="nofollow noreferrer">node status</a> condition set to <code>NetworkUnavailable: true</code> or some other condition which would make the pod unsuitable to run on that node.</p>
<p>If there is a signal or signals that you don't know or understand, there is a good chance there is a controller that uses that field or signal to accomplish its logic.</p>
<p><strong>EDIT:</strong></p>
<p>The node-controller is a part of the <a href="https://kubernetes.io/docs/reference/command-line-tools-reference/kube-controller-manager/" rel="nofollow noreferrer">kube-controller-manager</a>:</p>
<blockquote>
<p>The Kubernetes controller manager is a daemon that embeds the core
control loops shipped with Kubernetes. In applications of robotics and
automation, a control loop is a non-terminating loop that regulates
the state of the system. In Kubernetes, a controller is a control loop
that watches the shared state of the cluster through the apiserver and
makes changes attempting to move the current state towards the desired
state. Examples of controllers that ship with Kubernetes today are the
replication controller, endpoints controller, namespace controller,
and serviceaccounts controller.</p>
</blockquote>
<p>Logically, each controller is a separate process, but to reduce complexity, they are all compiled into a single binary and run in a single process.</p>
<p><strong>EDIT_2</strong>:</p>
<p>Based on your latest comments, we have 2 additional points to address:</p>
<blockquote>
<ol>
<li>&quot;how the node-controller processes the node health check&quot;</li>
</ol>
</blockquote>
<p>While implementing k8s, you probably don't need to know this level of detail. All the details which should be useful for you are already in the <a href="https://kubernetes.io/docs/concepts/overview/components/#kube-controller-manager" rel="nofollow noreferrer">linked public docs</a>. There is no need to worry about that but I understand that it brought the more practical question:</p>
<blockquote>
<ol start="2">
<li>I am not sure how much load a big cluster can generate.</li>
</ol>
</blockquote>
<p>This is where the <a href="https://kubernetes.io/docs/setup/best-practices/cluster-large/" rel="nofollow noreferrer">Considerations for large clusters</a> comes to help. It will show you how to handle big clusters and which tools are there at your disposal when it comes to managing them.</p>
