Kubernetes Workloads: CronJobs
Create a CronJob, trigger Jobs manually, limit job history, suspend the schedule, and observe all three concurrencyPolicy modes: Allow, Forbid, and Replace.
Focused, hands-on DevOps and server-side problems with hints, feedback, and automated solution checks.
Create a CronJob, trigger Jobs manually, limit job history, suspend the schedule, and observe all three concurrencyPolicy modes: Allow, Forbid, and Replace.
Start with nodeSelector for simple node targeting, then upgrade to node affinity for expressive matching that nodeSelector cannot handle.
Use LimitRange to set per-pod resource defaults and ResourceQuota to cap total namespace consumption.
See how Kubernetes determines BestEffort, Burstable, and Guaranteed classes from resource configuration - and which pods get evicted first under pressure.
See how CPU and memory requests influence where pods land - and what happens when no node can fit them.
Use PriorityClass to guarantee critical pods get scheduled even when the cluster is under resource pressure.
Spread pods evenly across nodes and availability zones using maxSkew and zone-aware topology keys.
See why taints and tolerations alone or node affinity alone are not enough to fully control pod placement on dedicated nodes.
Co-locate pods that belong together and keep apart pods that should not share a node using affinity and anti-affinity rules.