The Kubernetes ArchitectureTo start off, what is a Kubernetes Cluster? You can see it in the diagram below. Kubernetes clusters follow a master-slave system where a master control panel controls individual nodes. It uses labels as nametags to identify things. It may run queries based on these labels. The Kubernetes Master Control Panel consists of the following:
- API Server – handles REST requests and updates API object states in etcd.
- Controller Manager – daemon that manages core control loops, like Daemonset Controller and Replication Controller. Monitors the cluster’s shared state and makes alterations to move from current to desired state.
- Scheduler – matches available resources with the demands of the workload.
- etcd – stores the configuration data and current state of the entire cluster. Used as a reference for other components to go into their desired states.
- Kubelet – runs the node. It starts, stops, and maintains the application containers (which are grouped by pods).
- Kube-proxy – Kubernetes network proxy running on the node as well as load balancer. Reroutes traffic to the correct container according to request.
- cAdvisor – collects resource usage and performance data on each node
Kubernetes architecture diagramYou can find a more in-depth look at the Kubernetes Digitalocean tutorial, an excellent Kubernetes tutorial for beginners. Be sure to read more about how Kubernetes can help you, why you should use it to Dockerize your apps, and a Kubernetes tutorial for AWS. If you want to get your business fast-tracked on Kubernetes, find out how we can help you. And don’t forget to check out a Kubernetes tutorial video below. https://www.youtube.com/watch?v=Q4W8Z-D-gcQ&feature=youtu.be