In each node, we have a couple of components. The kubelet interacts with the API server to update the state and to start new workloads that have been invoked by the scheduler.

Kube-proxy provides basic load balancing and directs the traffic destined for specific services to the proper pod on the backend. Refer to the Services section later in this chapter.

Finally, we have some default pods, which run various infrastructure services for the node. As we explored briefly in the previous chapter, the pods include services for Domain Name System (DNS), logging, and pod health checks. The default pod will run alongside our scheduled pods on every node.