Command Palette

Search for a command to run...

Hectal
Phase 1Beginner2 of 10 in Kubernetes

Core Workload Objects

Deployments, Services, StatefulSets, Jobs, and DaemonSets — the five object types that describe almost everything you'll ever actually run.

Phase 0 introduced the raw pod and showed exactly why you'd never manage one directly. This phase covers the real objects that do — each one solving a specific, distinct shape of workload: stateless apps that scale freely, stateful apps that need stable identity, one-off jobs, and per-node system agents.

0/5 · 0%
5 topics ~70 min 14 code blocks & diagrams
Start with the first topic
1
1.1

Deployments & ReplicaSets

A Deployment describes the desired state of a stateless application — how many copies, which image — and handles creating, healing, and rolling out updates to the pods underneath it automatically.

14 min 1 diagram 2 code practice

2
1.2

Services: ClusterIP, NodePort, and LoadBalancer

Pods get a new, unpredictable IP address every time they're recreated — a Service gives a set of pods one stable address that never changes, automatically routing to whichever healthy pods currently exist.

14 min 1 diagram 2 code practice

3
1.3

StatefulSets vs Deployments

A Deployment's pods are fully interchangeable clones; a StatefulSet's pods each get a stable, unique identity and their own persistent storage — exactly what a real database or any stateful workload actually needs.

14 min 1 diagram 1 code practice

4
1.4

Jobs & CronJobs

A Job runs a pod to completion exactly once (or a set number of times) and stops — a CronJob does the same thing on a recurring schedule — for the genuinely common 'run this task, don't keep it running forever' shape of work.

14 min 3 code practice

5
1.5

DaemonSets: One Pod Per Node

A DaemonSet guarantees exactly one copy of a pod runs on every (or every matching) node in the cluster — the correct tool for genuinely per-node infrastructure like log collectors and monitoring agents.

14 min 1 diagram 2 code practice