Risk · 29 checks
Reliability.
Production-shape issues that cause incidents and rework: single replicas, missing requests and limits, missing probes. ZopNight runs 29 checks for reliability findings across AWS, Azure and Google Cloud.
Free to start. No card. The playground just needs your work email.
29checks
3providers
1check fixable in the product
Riskwhere it shows up
AWSAzureGoogle CloudKubernetes
Every reliability check.
Most severe first.
Autoscaler at Max CapacityDaemonSet Not Fully ScheduledDeployment Not Fully ReadyLiveness and Readiness Share One HandlerMissing CPU/Memory RequestsNode Not ReadyNode Under Disk PressureNode Under Memory PressureNode Under PID PressurePod Disruption Budget Allows No DowntimePod Disruption Budget Blocks All Voluntary DisruptionsStatefulSet Not Fully ReadyAutoscaler Allows Scale to ZeroAutoscaler Cannot Scale Past One ReplicaAutoscaler Has No MetricsContainer Image Tag Latest or MissingDeployment Uses Recreate StrategyFailed JobIngress Has No AddressLoadBalancer Service Stuck PendingMissing CPU/Memory LimitsMissing Liveness ProbeMissing Readiness ProbeSingle Replica DeploymentStatefulSet Has No Headless ServiceWorkload Missing Topology SpreadAutoscaler Pinned at One SizeMissing Startup ProbeStorageClass Uses Immediate Binding
Find the reliability findings in your account.
Connect a read-only role and every one of these runs on the first pass.
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.