Cicd documentation layout
Download 6.25 Mb.
|
- Navigate this page:
- 9.6. Kubernetes Architecture
- 9.8. PODs
9.5. Benefits of Kubernetes:Kubernetes is backed by the Cloud Native Computing Foundation (CNCF). Service discovery and load balancing Storage orchestration Automated rollouts and rollbacks Automatic bin packing Self-healing Secret and configuration management 9.6. Kubernetes Architecture:9.7. Components of Kubernetes:Master Components: Kube-apiserver: Component on the master that exposes the Kubernetes API. It is the front-end for the Kubernetes control plane. Etcd: Consistent and highly-available key value store used as Kubernetes’ backing store for all cluster data. Kubernetes cluster uses etcd as its backing store Kube-scheduler: Component on the master that watches newly created pods that have no node assigned, and selects a node for them to run on. Kube Controller Manager: It is a separate process, but to reduce complexity, they are all compiled into a single binary and run in a single process. Node Components: Kubelet: An agent that runs on each node in the cluster. It makes sure that containers are running in a pod. Kube-proxy: It is a network proxy that runs on each node in your cluster, implementing part of the Kubernetes service concept. Container Runtime: The container runtime is the software that is responsible for running containers. 9.8. PODs:A Pod is the basic execution unit of a Kubernetes application–the smallest and simplest unit in the Kubernetes object model that you create or deploy Pods that run a single container. The “one-container-per-Pod” model is the most common Kubernetes use case; in this case, you can think of a Pod as a wrapper around a single container, and Kubernetes manages the Pods rather than the containers directly. Pods that run multiple containers that need to work together. A Pod might encapsulate an application composed of multiple co-located containers that are tightly coupled and need to share resources. Pods are managed by a replication controller, which creates and destroys replicas of pods as needed. Individual pods can also be created outside of a replication controller. Pods have labels for the application name, role, environment, version, etc. Each of these can be combined in order to select all pods with a certain role, a certain application, or a more complex query Download 6.25 Mb. Share with your friends:
|