Kubernetes
Intermediate
API Pods Restart Across the Rollout
Every api replica is in CrashLoopBackOff and the Deployment has shown 0 of 3 available for ten minutes.
Free simulated incident practice
Practice Kubernetes incidents without setting up a cluster.
A workload can exist without being ready to serve traffic. These Kubernetes exercises let you practise moving from an alert to the relevant workload evidence in a simulated terminal. Start a brief, inspect the system, make a justified change and check whether the incident has recovered.
Separate scheduling, startup and readiness
Describe where the workload stops making progress before choosing a fix. A pod waiting to start, a repeatedly exiting process and an application failing readiness represent different investigation paths.
Follow the request path
For a reachability problem, compare the application state with the resources that route traffic to it. For a rollout problem, examine the change and its observed effect. Keep your next check tied to a question you can answer.
Verify more than object state
A resource showing a healthy status is one observation. Check the behaviour the alert described, complete the scenario recovery checks and explain the smallest change that restored it. The aim is a repeatable investigation, not memorising one command.
Put the method into practice.
Open a brief to see the symptoms, then launch the incident. The solution is yours to find.
Kubernetes
Intermediate
Webapp Pods Never Become Available
The migrated webapp has shown 0 of 1 available replicas from the moment it was applied to the new cluster four minutes ago.
Kubernetes
Beginner
Order Scoring Pods Keep Restarting
Both order-scoring worker pods die within seconds of every start, and the orders.score backlog keeps climbing.
Kubernetes
Intermediate
Checkout Pods Never Start
Ten minutes after tonight's release, the checkout Deployment has 0 of 2 replicas available and neither pod has ever started.
Kubernetes
Intermediate
Catalog Service Has No Backends
Calls to the catalog Service are refused even though both catalog pods are Running and Ready.
Kubernetes
Intermediate
Payment Pods Stuck Before Startup
The payment pod has been stuck before startup for ten minutes, leaving the payment Deployment with zero ready replicas.
Kubernetes
Intermediate
Report Workers Remain Pending
The report Deployment has run zero workers for ten minutes; its only pod is still waiting to be scheduled.
Kubernetes
Intermediate
Gateway Pods Run but Receive No Traffic
Both gateway pods have been Running for ten minutes and neither has ever become Ready, so no gateway replica is eligible for traffic.
Kubernetes
Advanced
Ledger Rollout Leaves Every Pod Crashing
Both pods from the new ledger revision crash on startup, leaving one old pod to carry every ledger write.
Kubernetes
Advanced
Ledger Deployer Is Forbidden to Patch
The payments deploy job's service account gets Forbidden on every Deployment patch, so the ledger change it carries cannot roll out.
Kubernetes
Advanced
Sensor Agent Crash-Looping on Every Node
The endpoint sensor on all five fleet-east nodes has been crash-looping.
What kind of lab is this?
FixOps runs simulated systems and a terminal designed for its scenarios. It does not provision a real server or cluster. Use it to rehearse investigation and recovery, and use a real environment when you need unrestricted tooling or production experience.
There is no interview pass guarantee or certification. You can start as a guest in the browser or use the Android app. If the concepts feel unfamiliar, work through a learning track before trying another incident.
Your pager is ready.
Free, instant, and it works on your phone. No signup: start as a guest and save your progress later.