The cloud controller manager does not exist on clusters that are entirely on-premises. Only those controls specific to the cloud provider will run.

cloud-controller-manager: If the cluster is partly or entirely cloud-based, the cloud controller manager links the cluster to the cloud provider’s API.

Service Account and Token controllers: Allocates API access tokens and default accounts to new namespaces in the cluster.

Endpoints controller: Connects Pods and Services to populate the Endpoints object.Node controller: Monitors the health of each node and notifies the cluster when nodes come online or become unresponsive.Replication controller: Ensures the correct number of pods is in existence for each replicated pod running in the cluster.kube-controller-manager: Although a Kubernetes cluster has several controller functions, they are all compiled into a single binary known as kube-controller-manager.Ĭontroller functions included in this process include:.kube-scheduler: When a new Pod is created, this component assigns it to a node for execution based on resource requirements, policies, and ‘affinity’ specifications regarding geolocation and interference with other workloads.Information in etcd is generally formatted in human-readable YAML (which stands for the recursive “YAML Ain’t Markup Language”). etcd is highly available and consistent since all access to etcd is through the API server. etcd: The key value store where all data relating to the cluster is stored.External communications via command line interface (CLI) or other user interfaces (UI) pass to the kube-apiserver, and all control planes to node communications also goes through the API server. As its name suggests the API server exposes the Kubernetes API, which is communications central. A Kubernetes control plane is the control plane for a Kubernetes cluster.

What is kubernetes controller