Kubernetes Workload Resources: Difference between revisions
No edit summary |
|||
| Line 4: | Line 4: | ||
=Overview= | =Overview= | ||
Workload resources exist to create and manage Pods, which should not usually be created directly. Various workload resources implement different pod utilization patterns. | Workload resources exist to create and manage Pods, which should not usually be created directly. Various workload resources implement different pod utilization patterns. | ||
The pod-managing resources described here are some times referred to as higher-level pod controllers or "templated controllers". <font color=darkkhaki>These controllers are part of and supervised by the controller manager</font>. | |||
=TODO= | =TODO= | ||
Revision as of 23:42, 11 July 2023
Internal
Overview
Workload resources exist to create and manage Pods, which should not usually be created directly. Various workload resources implement different pod utilization patterns.
The pod-managing resources described here are some times referred to as higher-level pod controllers or "templated controllers". These controllers are part of and supervised by the controller manager.
TODO
Workload Resource
Describe the relationship between pod, deployment, ReplicaSet and workload resources.
Controller
TODO: https://kubernetes.io/docs/concepts/workloads/pods/#pods-and-controllers
A workload resource has an associated controller. The controller handles replication, rollout and automatic healing in case of pod failure. For example if a node fails, a controller notices that the pods on that node have stopped working and creates replacement pods, which are scheduled on healthy nodes.
Workload resources:
- Deployment
- StatefulSet
- DaemonSet
- Jobs
- CronJob