Kubernetes cost optimization tools usually offer cluster-level scheduling: stop the whole cluster at night, start it in the morning, save the compute spend in between. The savings are real but the blast radius is bigger than most teams realize. Stopping the cluster takes the platform namespaces down too, which means the operators that other teams depend on go silent, the ingress controllers stop responding, and the cluster autoscaler cannot react to morning traffic until the cluster comes back.
Namespace-level scheduling fixes the scope problem. The stop runs only against the namespaces an operator actually wants to pause: dev, qa, staging, demo. Platform namespaces (kube-system, the ZopNight controller, the service mesh, the helm operator) stay online. Operators that depend on the cluster being reachable continue to work. The savings are smaller per stop, but the impact is contained to the namespaces that should be paused.
This article covers when namespace-level scheduling beats cluster-level scheduling, how system namespaces are protected, and how HPAs and PodDisruptionBudgets are restored byte-accurately on Start.
This guide keeps the theory short and spends most of its length on what you can actually do. Every recommendation here is one ZopNight can help you execute, starting from a read-only connection.
When cluster-level scheduling makes sense
Cluster-level scheduling is the right choice when every namespace on the cluster has the same runtime profile. A pure-dev cluster used only during business hours can be stopped overnight without consequence. A staging cluster used for nightly load tests stays online overnight and stops during the day. Single-purpose clusters get the maximum savings from cluster-level scheduling because the platform overhead is the same as the workload overhead.
When namespace-level scheduling is the better fit
Most production-adjacent clusters host a mix: the platform namespaces (operators, ingress, service mesh), the dev namespaces, the qa namespaces, the demo namespaces, sometimes a shadow-production namespace for performance testing. Stopping the cluster takes the platform down too. Stopping only the dev and qa namespaces keeps the platform online and trims the bill where the workloads actually run. This is the common case for shared engineering clusters.
System namespace protection
ZopNight namespace-level scheduling excludes kube-, zopnight-, istio-, helm-, and the default namespace by design. The exclusion is built into the scheduler, not configured per cluster, so an operator cannot accidentally stop kube-system through a misconfigured rule. The default namespace is included in the exclusion because it usually hosts ad-hoc operator workloads (debug pods, manual port-forwards) that should not be killed on a schedule.
HPA and PDB restore behavior
On Stop, the scheduler captures the spec of every HorizontalPodAutoscaler and PodDisruptionBudget in the namespace, then removes them. HPAs are removed so the scale-to-zero replica count is not immediately overridden by autoscaling. PDBs are removed because a min-available constraint would block the scale-to-zero. On Start, the captured spec is restored byte-accurately, then Deployments and StatefulSets scale back to their original replica counts and CronJobs un-suspend. The captured spec is hashed and recorded on the activity log so a later audit can confirm the restore matches the original.
Key takeaways
- Cluster-level scheduling suits single-purpose clusters where every namespace has the same runtime profile.
- Namespace-level scheduling suits shared clusters where platform namespaces must stay online while dev or qa stops.
- System namespaces (kube-, zopnight-, istio-, helm-, default) are excluded by the scheduler as a platform-level guarantee.
- HPAs and PDBs are captured on Stop, removed to allow scale-to-zero, and restored byte-accurately on Start.
- The captured spec hash on the activity log lets a later audit confirm Start matches the original state.
Where ZopNight fits
ZopNight turns this from reading into doing. It ships 490 built-in audit rules across AWS (216), GCP (127), and Azure (147), 124 of those recommendations are wired to act end to end, 28 one-click and 96 guided, and it starts read-only so you can see the opportunity before you act on any of it. The most direct place to begin is scheduling non-production resources to your working hours, which is covered in the FinOps guide and shown concretely for AWS EC2.
How ZopNight schedules non-production resources
The loop that does this is deliberately mechanical, and it starts read-only. You connect your cloud provider with a read-only role, and ZopNight discovers every non-production resources across your regions and accounts. It records a per-action permission verdict for each one, so you can see where it can list a resource but not yet stop it, and you review that inventory, filter it by status or type, and search for the specific resources you care about before anything is scheduled.
Scheduling itself is a cron you write once in plain terms, stop at 7 PM, start at 8 AM on weekdays, pinned to your timezone so the jobs fire at local business hours rather than UTC. A weekly 24-hour grid shows the schedule visually so you catch gaps and overlaps before you save, and an estimate of active versus inactive hours appears before you commit. Resources attach individually or bundle into groups like “dev-cluster” or “staging-db” so a whole environment follows one cadence.
Actions run in dependency order, so a database comes up before the app server that depends on it. When something needs to stay up, an override forces a non-production resources ON or OFF for a defined window, carries a reason so teammates understand why it exists, and expires automatically so nothing is left running by accident. If a start or stop fails, ZopNight retries up to three times and falls back to a dead-letter queue rather than silently dropping the action, and every state change lands in an audit trail that records whether a schedule, an override, or a specific user triggered it.
Beyond the schedule: recommendations, rightsizing, and showback
Scheduling is the fastest lever, but it is one of several. ZopNight ships 490 built-in audit rules across AWS (216), GCP (127), and Azure (147) that flag idle, oversized, and orphaned resources, and each recommendation shows the current monthly cost next to the estimated optimized cost so you act on the largest first. 124 of those recommendations are wired to act end to end, 28 one-click and 96 guided: one-click actions run immediately behind an admin-approval gate, and guided actions add a type-to-confirm review so you check the change before it lands. You mark a recommendation applied once you act, or dismiss the ones that do not fit.
Idle detection reads CPU, network, and connection metrics over a rolling window to separate a genuinely idle resource from one with real but intermittent traffic. Rightsizing is guided and computed from measured utilization over a real window, never a flat 24/7 assumption, so the projected figure matches the bill you actually see. For steady-state fleets, VM autoscaling runs in one of three modes derived from the credential’s permissions: monitor, recommend, or autopilot.
What is left after optimization gets attributed rather than hidden. Showback splits shared cost across owning teams and rolls up by cloud tag, GCP label, or Azure tag, with a Sankey cost-flow view that traces spend across provider, account, type, and team and a savings overlay that points straight at the reclaimable flows. A daily anomaly job writes root-cause markers onto the cost trend, an instance resize, a new resource, a reservation expiry, a failed schedule, so a spike explains itself instead of prompting a manual hunt. And 43 read-only tools expose the same data to an AI assistant over MCP, so you can ask an assistant in Claude, Cursor, or Codex for the same numbers.
Best practices that keep the savings
A few habits separate teams that hold onto the savings from teams that watch them drift back:
- Start with non-production and prove it there. Development, staging, QA, and demo environments carry almost no risk and the largest idle share, so they are the right place to build confidence before anyone considers production.
- Schedule by group, not by hand. Bundling an environment into a group like “staging” means one cadence covers every resource in it, and resources you add later inherit the schedule instead of being quietly forgotten.
- Use overrides instead of disabling schedules. When a late deploy needs a box overnight, a time-boxed override with a written reason keeps the schedule intact and expires on its own, so a one-off exception never becomes a permanent leak.
- Watch the audit trail and notifications. Every start, stop, and failure is logged and can post to Slack, Teams, or Google Chat, so a failed action is visible the moment it happens rather than discovered on the next invoice.
- Treat it as an operating rhythm, not a cleanup. The teams that keep the bill down review recommendations on a cadence and let the automation run continuously, instead of a one-off spring-clean that snaps back the moment attention moves on.
Getting started
Getting started is intentionally low-stakes:
- Connect your cloud provider with a read-only role. Nothing is scheduled or changed at this stage.
- Let ZopNight discover your non-production resources and review exactly what it found, filtered by account, region, and status.
- Create a schedule in your timezone and attach the non-production resources or groups you want it to cover.
- Watch the first cycle run, with Slack, Teams, or Google Chat notifications on every start, stop, and failure, then layer in idle cleanup and guided rightsizing.
Production stays excluded by default throughout, and because discovery and recommendations are read-only, you can prove the value before you enable a single action.
Questions we get a lot.
If yours isn't here, email us and we'll answer directly.
Can I schedule a namespace and the cluster at the same time?
You can but it usually creates conflicts. If the cluster stops while a namespace schedule says Start, the namespace Start fails until the cluster restarts. Pick one level of scope per environment. Use cluster-level for single-purpose clusters and namespace-level for shared clusters.
What if a workload is added between Stop and Start?
New workloads added between Stop and Start are not auto-managed by the schedule. They run as the user created them. The activity log shows the drift (workloads present on Start that were not captured on Stop) so operators can decide whether to include them in the next cycle.
Does stopping a resource delete my data?
No. A scheduled stop preserves attached storage exactly as a normal power-off would; ZopNight stops compute, it never terminates or deletes resources. Your data is intact when the resource starts again.
What access does ZopNight need to begin?
A read-only role. Discovery, cost reporting, and recommendations all run read-only, and ZopNight records a per-action permission verdict so you can see exactly what a credential can and cannot do before you grant anything more.
What happens if a start or stop action fails?
ZopNight retries automatically up to three times, then falls back to a dead-letter queue rather than dropping the action silently. The failure surfaces in the action status and can notify your Slack, Teams, or Google Chat channel.
Which clouds are supported?
AWS, GCP, and Azure from one platform, including Databricks across all three. Schedules, groups, overrides, and recommendations work the same way regardless of provider.