Kubernetes Component Introduction

Master node

Kube-apiserver

Provides a unique operation entry for the resource object, and all other components manipulate the resource object through the API it provides;

Etcd

Distributed key-value storage System. Used to keep cluster status, such as pod, service, and other object information

Kube-controller-manager

Responsible for maintaining the status of the cluster, such as fault detection, auto-scaling, rolling updates, etc.

Cloud-controller-manager

To handle regular background tasks in a cluster, one resource corresponds to a controller, and Controllermanager is responsible for managing those controllers.

Kube-scheduler

Responsible for the scheduling of resources, according to scheduled scheduling strategy to the pod scheduling to the corresponding machine responsible for resource scheduling, according to the scheduled scheduling strategy to the pod scheduling to the corresponding machine

Node nodes

Kubelet

Responsible for all life cycle management of pod creation, modification, monitoring and deletion on this node (nodes), meanwhile, Kubelet periodically "escalate" the status information of the bin to Apiserver

Kube-proxy

Implement POD network agents on node nodes, maintain network rules and four-tier load balancing work

Docker

Docker-damon components

Rkt

Support Container as an alternative to Docker

Supervisord

Process Management services to keep the Docker service running

Fluentd

Reference Link: https://kubernetes.io/docs/concepts/overview/components/#supervisord

Kubernetes Component Introduction