Kubernetes Cost Optimization: Explained

Kubernetes has become the default platform for deploying containerized applications, but it has also become one of the most expensive items on the cloud bill. The abstraction layer that makes Kubernetes flexible for developers also obscures the underlying infrastructure costs.

For non-production clusters, the waste is even higher because these clusters often mirror production sizing but handle negligible traffic.

Optimizing Kubernetes costs requires working at three levels: the cluster level (node pool sizing and scheduling), the workload level (resource requests and limits), and the organizational level (namespace cost allocation and accountability).

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.

Node pool scheduling

The most impactful Kubernetes cost optimization is scheduling non-production cluster node pools to scale to zero outside business hours. The control plane cost is minimal (free on GKE and AKS, $0.10/hour on EKS), but worker nodes running c5.2xlarge or equivalent instances cost hundreds of dollars per month each. Scaling a 5-node dev cluster to zero at night saves approximately $2,000/month per cluster. ZopNight handles the complexity: cordoning nodes, draining pods, scaling the node group, and reversing the process in the morning.

Resource requests and limits

Kubernetes schedules pods based on resource requests (guaranteed minimum) and limits (maximum allowed). Without requests, the scheduler cannot pack pods efficiently, it does not know how much each pod needs. Without limits, a single pod can consume an entire node. Set requests based on observed P50 utilization and limits based on P99. Use vertical pod autoscaler (VPA) in recommendation mode to get data-driven suggestions. Avoid setting requests equal to limits unless you need guaranteed QoS, it prevents the scheduler from over-committing.

Cluster autoscaler tuning

The default cluster autoscaler settings are conservative, keeping nodes around even when utilization is low. For non-production clusters, reduce the scale-down delay from 10 minutes to 2-3 minutes, lower the utilization threshold, and enable scale-to-zero for node pools. For production, keep conservative settings but ensure the autoscaler can add nodes quickly for traffic spikes. Use multiple node pools with different instance types to optimize for different workload profiles.

Namespace cost allocation

Allocate Kubernetes costs to teams by namespace. Use labels and annotations to track which team owns each namespace. Multiply the resource requests in each namespace by the per-unit cost of the underlying nodes. This gives each team visibility into their Kubernetes spending and creates accountability for optimization. Tools like ZopNight aggregate this data alongside other cloud costs for a unified view.

Key takeaways

• Scheduling non-production node pools to zero is the highest-impact K8s optimization.
• Set resource requests on every pod to enable efficient scheduling and packing.
• Allocate costs by namespace to drive team-level accountability.

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.