Pod¶
Pod is the smallest and most basic unit in the Kubernetes object model, representing a single instance of an application.^[400-devops-06-kubernetes-k8s-ithelp-day3-readme.md]
Composition¶
A Pod consists of one or more containers—typically Docker images—and several controllers.^[400-devops-06-kubernetes-k8s-ithelp-day3-readme.md] Similar to Docker, Pods support persistent storage (volumes) which allows them to run stateful applications.^[400-devops-06-kubernetes-k8s-ithelp-day3-readme.md]
Function and Scheduling¶
Pods function as the application load within the cluster and are hosted on Worker Nodes.^[400-devops-06-kubernetes-k8s-ithelp-day3-readme.md] The kube-scheduler is responsible for determining the most suitable Worker Node for each new Pod based on filtering and scoring policies.^[400-devops-06-kubernetes-k8s-ithelp-day3-readme.md] Once scheduled, the kubelet service on the Node ensures that the containers defined in the Pod are running.^[400-devops-06-kubernetes-k8s-ithelp-day3-readme.md]
Related Concepts¶
- Kubernetes
- [[Node]]
- [[Container runtime engine]]
- Kubelet
Sources¶
^[400-devops-06-kubernetes-k8s-ithelp-day3-readme.md]