# Namespace-level scheduling + resize remediation

> Kubernetes scheduling now works at the namespace boundary across EKS, GKE, and AKS: stop scales workloads to zero, suspends CronJobs, and saves the full state to replay on start. Auto-remediation gains a Resize action with five new right-size rules, and the platform now records true peak and trough metrics so bursty workloads aren't smoothed away into unsafe rightsizing.

Source: https://zop.dev/changelog/v1-10-0
Published: 2026-05-14 · Tags: zopnight, zopday, kubernetes, scheduling, auto-remediation

---

Start and stop whole Kubernetes namespaces.

## New

- Namespace-level start / stop across EKS, GKE, and AKS: stop scales Deployments and StatefulSets to zero, suspends CronJobs, and snapshots replicas, HPA, and PDB to replay on start; system namespaces are protected at both discovery and execution
- Auto-remediation adds Resize, five new right-size rules: AWS Lambda memory, AWS EC2 instance type, AWS EBS IOPS / throughput, GCP machine type, and Azure VM SKU

## Improved

- The Use existing VPC wizard now explains why a VPC is unselectable (needs at least one subnet and one NAT gateway) and offers a one-click Create new VPC instead
- Provisioner cluster jobs complete about 5 minutes faster by chaining quick steps within a single cycle