Skip to main content
Reliability · High severity

Pod Disruption Budget Allows No Downtime

No pod may ever be voluntarily evicted, so a cluster upgrade hangs indefinitely waiting on this workload.

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

3clouds covered
Highseverity
Riskwhere it shows up
Manualfix, change spelled out

AWSAzureGoogle CloudKubernetes

Found, explained, handed over.

Exposure and fragility, security posture and single points of failure.

01

Detect

ZopNight checks this automatically across AWS, Azure and Google Cloud, with read-only access to the account.

02

Explain

Every finding says exactly what to change: Raise maxUnavailable on the pod disruption budget.

03

Fix

The finding opens with the change already spelled out, so the fix is one ticket, not an investigation.

Applies to
EKS Pod Disruption Budgets on AWS, AKS Pod Disruption Budgets on Azure, GKE Pod Disruption Budgets on Google Cloud
Category
Reliability. Production-shape issues that cause incidents and rework: single replicas, missing requests and limits, missing probes.
Where it appears
The Risk tab of Recommendations, with every affected resource listed.
Rule IDs
RC-1748 RC-1848 RC-1948

Related checks

See the reliability findings in your account.

Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.

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·