Introduction to the core components of Kubernetesk

This article gives you an introduction to the core components of Kubernetesk. The editor thought it was very practical, so I shared it with you to learn. The following information is about the core components of Kubernetesk.

1. Three components of core components

Second, configure the storage center (etcd service) can be defined as the entire K8S MYSQL database function (non-relational data), store cluster metadata information, the function is similar to ZK and so on. II. Kube-apiserver services

1. Provide REST API interface for cluster management (including authentication, data verification and cluster status change).

2. Responsible for the data exchange between other modules and assume the function of communication hub.

3. It is the entrance of resource quota control.

4. Provide a complete cluster security mechanism.

III. Kube-controller-manager service

1. It is composed of a series of controllers to monitor the status of the entire cluster through apiserver and ensure that the cluster is working as expected.

IV. Kube-scheduler service

1. The main function is to receive and dispatch Pod to suitable computing nodes, such as budget strategy and optimization strategy.

5. Kube-kubelet service

1. To put it simply, the main function of kubelet is to obtain the desired state of pod on the node (what container to run, the number of copies to run, how to configure the temple for network or storage, etc.) from somewhere, and call the corresponding container platform API to achieve this state.

2. Report the status of the current node to apiserver regularly for scheduling.

3. Clean up the image and container to ensure that the image on the node will not take up full disk space, and that exiting the container will not take up too many resources.

VI. Kube-proxy service

1. In K8S, the network agent running on each node and the carrier of service resources establish the relationship between pod network and cluster network (clusterip-podip).

2. Three commonly used traffic scheduling modes: Userspace\ Iptables\ ipvs (recommended by lvs)

3. Responsible for establishing and deleting scheduling rules, including updating scheduling rules, notifying apiserver of its own updates, or where to get other kube-proxy scheduling rule changes from apiserver to update itself.

VII. Understanding of network architecture

8. Experimental high availability topology diagram

After reading the above, do you have any further understanding of the core components of Kubernetesk? If you want to learn more skills or want to know more about it, you are welcome to follow the industry information channel. Thank you for reading.