Shulou(Shulou.com)06/02 Report--

This article mainly explains "what is Kubernetes architecture design and core component workflow". The explanation in this article is simple and clear and easy to learn and understand. Please follow the editor's train of thought to study and learn "what is Kubernetes architecture design and core component workflow".

Kubernetes is a complete container cluster management engine, which provides various mechanisms and interfaces to ensure the rapid release and healthy operation of applications, and provides rich command line tools (CLI) and API interfaces to facilitate interaction with the cluster. At the same time, Kubernetes provides multi-level security protection and isolation mechanism, multi-tenant application support, application lifecycle management, and scalable automatic resource scheduling mechanism. With multi-granularity resource quota management capabilities, unified configuration management components supported by multi-tenants, and multi-availability zone support, Kubernetes provides a complete set of container management tools to provide one-stop service for container cluster management.

Kubernetes architecture

The overall architecture of Kubernetes, as shown in the following figure:

Kubernetes mainly consists of the following core components:

Etcd saves the state of the entire cluster

Kube-apiserver provides a unique entry for resource operations and provides mechanisms such as authentication, authorization, access control, API registration and discovery.

Kube-controller-manager is responsible for maintaining the status of the cluster, such as fault detection, automatic extension, rolling updates, etc.

Kube-scheduler is responsible for resource scheduling and dispatches Pod to the corresponding machine according to the predetermined scheduling policy.

Kubelet is responsible for maintaining the life cycle of the container and is also responsible for the management of Volume (CVI) and network (CNI).

Container runtime is responsible for image management and the actual operation of Pod and container (CRI). The default container runtime is Docker

Kube-proxy is responsible for providing service discovery and load balancing within cluster for Service.

In addition to the core components, there are some recommended Add-ons:

Kube-dns is responsible for providing DNS services for the entire cluster.

Ingress Controller provides public network access for services.

Heapster provides resource monitoring

Dashboard provides GUI

Federation provides clusters across availability zones

Fluentd-elasticsearch provides cluster log collection, storage and query.

The following figure depicts the sequence diagram of the interaction between the Kubernetes components and the workflow of the object that created the pod:

Through the figure above, we can understand the interaction and workflow between the various components of pod when creating objects of Kubernetes, so that Kubernetes practitioners can better understand the role of various components of Kubernetes and how to interact with each other.

Thank you for your reading, the above is the content of "Kubernetes architecture design and core component workflow". After the study of this article, I believe you have a deeper understanding of what Kubernetes architecture design and core component workflow is, and the specific use needs to be verified in practice. Here is, the editor will push for you more related knowledge points of the article, welcome to follow!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.