Inspect the signals
Read a short incident brief. Reveal simulated diagnostic output and use hints when you need a nudge.
KUBERNETES / GUIDED PRACTICE
Read the signals.
Explain the cause.
A practice room for the first few minutes of an incident. Work through authored Kubernetes cases, collect evidence, and put your reasoning into words.
Browser-based. No cluster setup or account required.
10 core cases10 transfer casesYour practice notebook
practice / report-worker
SIMULATEDA FIRST LOOK AT THE INCIDENT
The worker keeps restarting.
The jobs are delayed. The restart count is climbing. Where would you look next?
Initial evidenceAUTHORED EXCERPT
Namespace: practice Pod: report-worker-7c8d9 READY STATUS RESTARTS 0/1 CrashLoopBackOff 5
Inspect the previous termination
A restart is a symptom. Find the evidence behind it.
Authored evidence, with links to Kubernetes documentation.
Guest practice stays on your device.
Written reasoning needs human review.
THE INVESTIGATION LOOP
A little structure
for a messy moment.
For individual DevOps engineers and learners who want to practice the steps of an investigation.
Make your case
Choose a diagnosis, cite supporting checks, and explain how the evidence connects to your answer.
Revisit the reasoning
Review the authored debrief, keep a note, and try a transfer case with a different failure mechanism.
Automated checks cover your selected diagnosis, required evidence, citations, and explanation length. They do not assess the quality of your explanation or certify operational readiness.
INSIDE THE LIBRARY
Familiar symptoms.
Different explanations.
CASE 01Beginner
The restarting report worker
Distinguish a restart symptom from a confirmed termination reason.
About 6 minutes Guided simulation
CASE 02Beginner
Healthy pods, unreachable service
Trace how a Service selects its backend pods.
About 7 minutes Guided simulation
CASE 03Intermediate
A release that never starts
Separate registry authentication failures from missing image tags.
About 8 minutes Guided simulation
Each core case has a related transfer case. Expect a changed signal or cause, then investigate again.
KEEP THE TRAIL
Your thinking deserves
a notebook.
Keep separate runs, notes, hints, and submitted-answer history. Return to a case without overwriting the path you took before.
Make your first field note- 01
Start with local practice
Your guest notebook lives in this browser. Search it by case title, notes, or written reasoning.
- 02
Take a backup with you
Export a readable Markdown report or a restorable JSON backup. Import a file or paste your JSON.
- 03
Choose what to share
On configured deployments, email accounts and explicit cloud sync are optional. Signing in alone does not upload your notebook.
BEFORE YOU START
A few clear boundaries.
Will this connect to my cluster?
No. Cases use authored terminal excerpts. OpsTriage does not run commands, connect to infrastructure, or perform remediation.
Do I need an account?
You can start free as a guest. An email account is optional where configured, and cloud upload or merge requires a separate action.
Does the app grade my explanation?
It checks that you supplied a minimum-length explanation. The meaning and quality need review by you, a peer, or a facilitator. These exercises are for self-study, not certification.
What happens to my practice data?
Guest practice is stored in this browser. Optional usage counts require consent and do not include answer or notes text. Cloud sync sends your notebook only when you explicitly choose it. Read the beta guide for the details.
YOUR NEXT INVESTIGATION
Start with a signal.
Follow the evidence.
Start free as a guest No account required. Your first case is waiting in the library.