Skip to content
Clairos Learn

Serving, containers, and resources · Lesson 10 of 17 · 6 min

Inspect pod resources

Resource requests, limits and observed use serve different roles. Compare the observation with the relevant boundary instead of treating all resource numbers as the same quantity.

Open the labCourse map
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

Resource requests, limits and observed use serve different roles. Compare the observation with the relevant boundary instead of treating all resource numbers as the same quantity.

Interpret the evidence

Review memory pressure near the 4096 MiB limit while retaining the distinct 2048 MiB request.

A tempting mistake

The memory request is always the termination limit.

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-010.json
{
  "fixture": "Fictional training data; not a live measurement.",
  "memory_request_mib": 2048,
  "memory_limit_mib": 4096,
  "observed_mib": 3900
}

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

$ jq .observed_mib /opt/ai-lab/cases/aiops-serving-resources-010.json
3900

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

$ printf '%s\n' 'review-memory-pressure' > /home/learner/lab/aiops-serving-resources-010-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 “review-memory-pressure” to stop being the justified action. Do not silently replace missing evidence with a guess.

Explain it

What does the evidence in “Inspect pod resources” justify?

Apply it elsewhere

A colleague concludes: “The memory request is always the termination limit.” What should you do?

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Review a deployment diffTry 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. 01Read 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
  2. 02Review a deployment diffRead a deployment diff for behavioral changes, not just additions and deletions. A replica change affects capacity and cost and should be reviewed against readiness and load.Practice
  3. 03Inspect GPU availabilityGPU visibility and available memory are separate observations. Measure free memory and runtime attachment before deciding whether the next model can be loaded.Practice

Case methodology: evidence, limits, decision