=== etcd ===
Consistent and highly-available key value store. Used for backing store for all cluster data. https://etcd.io/docs/
=== Kube-scheduler ===
Control plane component that watches for newly created Pods with no assigned node , and selects a node for them to run on.
Factors taken into account for scheduling decisions include: individual and collective resource requirements, hardware/software/policy constraints, affinity and anti-affinity specifications, data locality, inter-workload interference, and deadlines.
=== Kube-controller-manager ===
Control Plane component that runs controller processes; including Node controller, Replication controller, Endpoints controller, Service Account and Token controllers.
=== Cloud-controller-manager ===
A Kubernetes control plane component that embeds cloud-specific control logic. The cloud controller manager lets you link your cluster into your cloud provider's API, and separates out the components that interact with that cloud platform from components that just interact with your cluster.
=== Kubeadm =Node Components ==[https://github.com/kubernetes/kubeadm Kubeadm] is a [https://github.com/kubernetes/kubernetes/tree/master/cmd/kubeadm component of Kubernetes]. : Kubeadm is a tool built to provide best-practice "fast paths" for creating Kubernetes clusters. It performs the actions necessary to get a minimum viableNode components run on every node, secure cluster up and maintaining running in a user friendly way. Kubeadm's scope is limited to the local node filesystem pods and providing the Kubernetes API, and it is intended to be a composable building block of higher level toolsruntime environment.
=== Kubectl Kubelet ===An agent that runs on each node in the cluster. It makes sure that containers are running in a Pod .
=== Kube-proxy ===
kube-proxy is a network proxy that runs on each node in your cluster, implementing part of the Kubernetes Service concept.
=== Kube-scheduler Container runtime ===Control plane component The container runtime is the software that watches is responsible for newly created Pods with no assigned node running containers. Docker by default, it can also be CRI-O or possibly other implementations of the Container Runtime Interface. == Addons ==You probably need at least the DNS and selects a node for them to run onWeb UI [https://kubernetes.io/docs/concepts/cluster-administration/addons/ addons]. == Tools ===== Kubectl ===The [https://kubernetes.io/docs/reference/kubectl/overview/ <code>kubectl</code>] command line tool lets you control Kubernetes clusters.
Factors taken into account for scheduling decisions include=== Kubeadm ===[https://github.com/kubernetes/kubeadm Kubeadm] is a [https: individual and collective resource requirements, hardware/software/policy constraintsgithub.com/kubernetes/kubernetes/tree/master/cmd/kubeadm component of Kubernetes]. : Kubeadm is a tool built to provide best-practice "fast paths" for creating Kubernetes clusters. It performs the actions necessary to get a minimum viable, affinity secure cluster up and anti-affinity specifications, data locality, inter-workload interferencerunning in a user friendly way. Kubeadm's scope is limited to the local node filesystem and the Kubernetes API, and deadlinesit is intended to be a composable building block of higher level tools.
[[Category:Virtualization]]