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

This article mainly introduces "brief introduction to kubernetes". In daily operation, I believe many people have doubts about the brief introduction of kubernetes. The editor consulted all kinds of materials and sorted out simple and easy-to-use methods of operation. I hope it will be helpful to answer the doubts of "brief introduction to kubernetes"! Next, please follow the editor to study!

Kubernetes order

An application-oriented container cluster deployment and management system is provided. The goal of Kubernetes is to eliminate the choreography of physical / virtual computing

Kubernetes built on top of Docker can build a container scheduling service

The core concept is Container Pod.

Basic concept

Node (Node): a node is a host running in Kubernetes. Container group (Pod): a Pod corresponds to a container group consisting of several containers, and containers in the same group share a storage volume (volume). Container group life cycle (pos-states): contains all container state collections, including container group state types, container group life cycle, events, restart policies, and replication controllers. Replication Controllers: mainly responsible for specifying a number of pod to run together at the same time. Service (services): a Kubernetes service is a high-level abstraction of container group logic and also provides policies to access container groups. Volume (volumes): a volume is a directory to which the container has access. Labels: tags are used to connect a set of objects, such as container groups. Tags can be used to organize and select sub-objects. Interface permissions (accessing_the_api): firewall rules for ports, IP addresses and agents. Web interface (ux): users can operate Kubernetes through the web interface. Command line operation (cli): the kubecfg command. Etcd keeps the state of the entire cluster; apiserver provides the only entry for resource operation and provides mechanisms such as authentication, authorization, access control, API registration and discovery; controller manager is responsible for maintaining the state of the cluster, such as fault detection, automatic extension, rolling updates, etc. Scheduler is responsible for resource scheduling, dispatching Pod to the corresponding machines according to the predetermined scheduling policy Kubelet is responsible for maintaining the lifecycle of the container, and is also responsible for the management of Volume (CSI) and network (CNI). Container runtime is responsible for image management and the real operation of Pod and container (CRI). Kube-proxy is responsible for providing Service with service discovery and load balancing within cluster. At this point, the study on "brief introduction to kubernetes" is over. I hope you can solve your doubts. The collocation of theory and practice can better help you learn, go and try it! If you want to continue to learn more related knowledge, please continue to follow the website, the editor will continue to work hard to bring you more practical articles!

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.