Workloads for Kubernetess
Kubernetes workloads are the API objects that run your containers, including Pods, Deployments, ReplicaSets, Jobs, CronJobs and DaemonSets. A Pod is the smallest deployable unit, and higher level controllers create and replace Pods to keep the desired number running or to finish batch work.
Stage: Core Objects · Part of the Kubernetes roadmap · Last reviewed 19 November 2026
What to learn in Workloads
- Write a Pod manifest and explain why Pods are rarely created directly
- Create a Deployment and perform a rolling update and a rollback with kubectl
- Run a one-off task with a Job and a scheduled task with a CronJob
- Use a DaemonSet to run one Pod on every node
- Read labels and selectors to see which Pods a controller owns
Workloads interview questions
What is the difference between a Pod and a Deployment?
A Pod is one or more tightly coupled containers sharing network and storage, and if it dies it is not recreated by itself. A Deployment manages a ReplicaSet of Pods, keeps the requested replica count running, and provides rolling updates and rollbacks.
When would you use a DaemonSet?
Use a DaemonSet when exactly one copy of a Pod should run on each node, or on a selected set of nodes. Typical cases are log collectors, node monitoring agents and network plugins. New nodes automatically receive the Pod when they join the cluster.
Where Workloads fits in the Kubernetes roadmap
Workloads belongs to the Core Objects stage (intermediate level), which takes about 22 hours. The building blocks.
Other units in this stage
Back to the full Kubernetes roadmap