Workloads
Workloads are the first place where Kubernetes stops being infrastructure trivia and becomes an application operating model.
Topics
- Pods - A Pod is the smallest deployable unit: one network identity, one scheduling decision, and one shared local context for containers.
- Deployments And ReplicaSets - A Deployment is a rollout controller. ReplicaSets are the machinery it uses to keep the right number of Pods alive.
- StatefulSets - StatefulSet gives Pods stable identity and ordered behavior. It is for software that notices who it is.
- DaemonSets - A DaemonSet runs one copy of a Pod across selected nodes. It is how node-level services become cluster-wide.
- Jobs And CronJobs - Jobs are for completion, not serving. CronJobs add a clock to that contract.
- Autoscaling - Autoscaling is a feedback loop. It needs metrics, resource requests, and a workload that can survive replica changes.
Editorial Notes
- Keep the official docs as the citation layer.
- Keep this lab opinionated around homelab operations: verification, failure modes, and practical boundaries.
- Avoid copying upstream prose; cite it, then explain the operating model in our own language.
Sources
- Workloads - source path:
content/en/docs/concepts/workloads/_index.md, commit 8cc9e19b8eec8d5cf49eacd66f86a81648edb1a0. - Pods - source path:
content/en/docs/concepts/workloads/pods/_index.md, commit 8cc9e19b8eec8d5cf49eacd66f86a81648edb1a0. - Deployments - source path:
content/en/docs/concepts/workloads/controllers/deployment.md, commit 8cc9e19b8eec8d5cf49eacd66f86a81648edb1a0. - Kubernetes documentation is licensed under CC BY 4.0; these notes are original commentary and link back to the official source.