Note
This is where most of my familiarity is, deploying applications by providing a manifest that ArgoC uses. The control plane makes global decisions about the cluster and detects + responds to cluster events.
Consists of
kube-apiserver
- Exposes the kubernetes API (FE for the control plane) ectd
- Kind of like redis?
- High availability KV store
- Can be used as a backing store kube-scheduler
- Watches for new pods with no assigned nodes and tells the pod where to run kube-controller-manager
- Runs controller processes
- Many different controllers
- node controller
- endpoint slice controller
- etc… cloud-controller-manager
- Embeds cloud specific control logic
- Lets you link your cluster to a cloud provider API