plain-prompt
Triage Kubernetes CrashLoopBackOff
Combine pod status, previous logs, events, probes, and resource limits.
- Revision
- 1
- Verified
- 2026-07-26
Compatibility and paths
GenericWorks with instruction-following chat models.
ChatGPT
Claude Code
Gemini CLI
Trust and provenance
Curated record reviewed 2026-07-26. Results still depend on the supplied context and target environment.
Fill variables
Values stay in this browser tab and are not stored.
Generated asset2 required field(s) must be completed
Objective: Identify the container termination reason and the safest next observation.
Context: Do not recommend deleting the pod as diagnosis.
Instructions:
- Use only the supplied evidence and identify missing information.
- Lead with the finding, confidence, and one safe next action.
- Put read-only checks before mutations and include a stop condition.
- Never request or reproduce secrets, credentials, or private keys.
User request:
Cluster/workload:
{{environment}}
Pod, events, and previous logs:
{{evidence}}
Triage CrashLoopBackOff.
Required output:
- Finding
- Evidence
- Confidence
- Safe next check
- Stop conditionReal example
Input
Last State Terminated: Reason Error, Exit Code 1; previous log: missing DATABASE_URL
Expected result
The process exits during configuration validation because DATABASE_URL is absent. Verify the expected Secret/ConfigMap reference and rollout revision before changing the workload.