Kubernetes: Difference between revisions

@@ Line 8: / Line 8: @@
 === Kube-apiserver ===
+The API server is the front end for the Kubernetes control plane.
+The main implementation of a Kubernetes API server is [https://kubernetes.io/docs/reference/generated/kube-apiserver/ kube-apiserver]. kube-apiserver is designed to scale horizontally—that is, it scales by deploying more instances. You can run several instances of kube-apiserver and balance traffic between those instances.
+=== etcd ===
+Consistent and highly-available key value store. Used for backing store for all cluster data. https://etcd.io/docs/
 === Kube-controller-manager ===
@@ Line 20: / Line 26: @@
 === 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.
 [[Category:Virtualization]]