K8s workload scheduling
Schedule K8s namespaces across EKS/GKE/AKS so their workloads stop off-hours without affecting the cluster itself.
6 lessons. 1 quiz.
Read in order, or jump to what you need.
Why K8s is hard to cost-optimize
By the end of this lesson, you will be able to identify three structural reasons K8s defies traditional FinOps tooling, explain ZopNight's decoupled model, and architect namespace-level scheduling that preserves production.
Cluster → namespace → workload hierarchy
By the end of this lesson, you will be able to navigate the K8s parent-child hierarchy in ZopNight, find any specific workload via filters, and identify what is schedulable (the namespace) and what is not.
Scheduling a Deployment to zero replicas
By the end of this lesson, you will be able to configure scale-to-zero scheduling for the Deployments in a namespace, handle HPA integration, and resolve service dependencies during off-hours.
Suspending CronJobs
By the end of this lesson, you will be able to suspend K8s CronJobs to skip executions, resume them on schedule, and handle concurrent jobs gracefully.
Scheduling StatefulSets: careful with replicas
By the end of this lesson, you will be able to distinguish safe vs dangerous StatefulSet scheduling patterns, execute the safety checklist, and handle PVCs correctly during scheduling cycles.
Cross-cluster orchestration with groups
By the end of this lesson, you will be able to group K8s namespaces across multiple clusters, apply a single schedule across cluster boundaries, and choose the right grouping pattern.
Module quiz.
Take it once the lessons are done.