Debug Infrastructure Issues

Use this after readiness, rollout, or dependency failure. It diagnoses infrastructure; recovery is separate.

Prerequisites

Preserve the first failing readiness response, deployment/config diff, workload status, logs, and alert timeline before restart.

Inspect Compose containers or Kubernetes pods, Jobs, events, and rollout.
Compare mode, Secret keys, URLs, ports, origins, and release pin with the release.
Test Postgres connectivity, migrations, pools, and outbox age.
Test Redis connectivity, noeviction, persistence, groups, and pending entries.
Read exact readiness reason and correlated logs.
Inspect policy age, STS circuit, revocation snapshot, audit DLQ/replay, and evidence-loss latch.

Start with caracal status --json, Compose status/logs, or Kubernetes get/describe/logs.

Diagnosis is complete when one dependency, value, ceiling, or safety invariant explains readiness with log/metric evidence.

Do not delete volumes, reset streams, restore data, or clear evidence before selecting recovery.