Skip to content
Clairos Learn

Serving, containers, and resources · Lesson 7 of 17 · 8 min

List Kubernetes workloads

Pod readiness summarizes whether workloads can accept traffic under their probes. Running phase alone can coexist with zero ready containers.

Mastery 0/3Run itExplain itApply it
learner@clairosSimulated AI Ops lab
learner@clairos:~ $
↑ history · Tab complete · Ctrl+C cancel · Esc, Tab to leaveExit 0

Understand the pattern

Pod readiness summarizes whether workloads can accept traffic under their probes. Running phase alone can coexist with zero ready containers.

Interpret the evidence

Inspect why the running pod has zero ready containers before directing traffic to it.

A tempting mistake

Running phase overrides a failed readiness probe.

All names, measurements, prices, versions, and thresholds in this exercise are fictional training data. The evidence supports this bounded scenario, not a claim about a live provider.

Worked example and expected result
$ cat /opt/ai-lab/cases/aiops-serving-resources-007.json
{
  "fixture": "Fictional training data; not a live measurement.",
  "pod": "gateway-7d9",
  "phase": "Running",
  "ready_containers": 0,
  "total_containers": 1
}

Exit status: 0. The command completed successfully in the training fixture.

$ jq .ready_containers /opt/ai-lab/cases/aiops-serving-resources-007.json
0

Exit status: 0. The command completed successfully in the training fixture.

$ printf '%s\n' 'inspect-readiness-probe' > /home/learner/lab/aiops-serving-resources-007-decision.txt
(no output; exit 0)

Exit status: 0. The command completed successfully in the training fixture.

Try a variation

Name the assumption that would have to change for “inspect-readiness-probe” to stop being the justified action. Do not silently replace missing evidence with a guess.

Explain it

What does the evidence in “List Kubernetes workloads” justify?

Apply it elsewhere

A colleague concludes: “Running phase overrides a failed readiness probe.” What should you do?

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Describe a serving podTry an incident drill

Anonymous lesson and mastery progress lasts for this session. Sign in to keep synced lesson XP between sessions; mastery stays device-local. No speed bonus, lost lives, or hint penalties.

Keep learning

  1. 01Validate compose configurationConfiguration validation catches malformed deployment structure before activation. A syntactically valid Compose file still needs separate readiness and workload checks.Practice
  2. 02Describe a serving podPod description brings together events, scheduling and container state. Use the reported reason to choose a focused investigation.Practice
  3. 03Read pod logsContainer logs describe a particular process instance. After a restart, retain the prior instance evidence when it is needed to explain the failure.Practice