Skip to main content
AWS · 3 checks

EKS Pod Disruption Budgets on AWS,
checked for you.

ZopNight runs 3 checks on your EKS Pod Disruption Budgets in AWS, covering reliability and governance. Workloads are scheduled by namespace.

Sign inExplore the playground

Free to start. No card. The playground just needs your work email.

3checks
2categories
Manualfixes, spelled out
Yesscheduled with its namespace

AWSKubernetes

Every check, grouped by what it protects.

Each one opens with why it matters and exactly what to change.

Governance1

Missing tags and labels that break cost attribution, such as no environment, team or cost-centre value.

Pod Disruption Budget Matches No PodsLow

Reliability2

Production-shape issues that cause incidents and rework: single replicas, missing requests and limits, missing probes.

Pod Disruption Budget Allows No DowntimeHighPod Disruption Budget Blocks All Voluntary DisruptionsHigh

Find these on your own EKS Pod Disruption Budgets.

Connect a read-only role and ZopNight inventories the EKS Pod Disruption Budgets you run, then runs all 3 checks against them.

Start freeExplore the playground

Prefer to talk it through first? Book 20 minutes with the team.

  • $30M+annualised cloud spend under management
  • 550K+resources tracked since launch
  • 20-60%off the bill in the first month
  • SOC 2Type II report, plus ISO 27001

Figures published on zop.dev.

Multi-cloud automation· Production-ready in 30 min· SOC 2 · ISO 27001· 20–60% off the bill, first month· 4 platforms · 1 console· Multi-cloud automation· Production-ready in 30 min· SOC 2 · ISO 27001· 20–60% off the bill, first month· 4 platforms · 1 console·