Kubernetes Workload Resources: Difference between revisions
Jump to navigation
Jump to search
| Line 21: | Line 21: | ||
Workload resources: | Workload resources: | ||
* <span id='Deployment'></span>Deployment | * <span id='Deployment'></span>Deployment | ||
* StatefulSet | * <span id='StatefulSet'></span>StatefulSet | ||
* DaemonSet | * <span id='DaemonSet'></span>DaemonSet | ||
* Jobs | * <span id='Job'></span>Jobs | ||
* <span id='CronJob'></span> CronJob | |||
=To Distribute= | |||
====ReplicaSet==== | |||
Revision as of 23:18, 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.
TODO
Workload Resource
Describe the relationship between pod, deployment, ReplicaSet and workload resources.
Controller
Migrate from Kubernetes Higher Level Pod Controllers
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