HyperFleet Operational Readiness Audit

Run an operational readiness audit against local HyperFleet repositories to verify health probes, dead man's switch metrics, retry logic with exponential backoff, PDBs, resource limits, and graceful termination handling, producing a read-only report of production readiness gaps.

A production readiness audit evaluates Kubernetes deployment configurations by verifying PodDisruptionBudgets, resource limits, and health probes to identify resilience gaps and surface actionable remediation steps for on-call and engineering teams without modifying code.

Verify graceful shutdown and health probes by running an audit that checks functional health checks and graceful termination handling against HYPERFLEET-539 requirements, surfacing any operational readiness gaps in a structured read-only report.

No, the readiness audit is strictly read-only and does not modify code or configurations. It assesses deployment configurations, retry logic, and metrics to produce a structured report highlighting resilience gaps and recommended improvements.

Yes, the audit applies to general HyperFleet repositories and specifically monitors dead man's switch metrics and retry logic with exponential backoff to identify operational readiness gaps based on HYPERFLEET-539 requirements.

Run the operational readiness audit before promoting a change to production to verify repository readiness, identify blockers to production readiness, and surface recommended improvements for health probes, graceful shutdown, and deployment configurations.