Serving, containers, and resources
Inspect services, containers, Kubernetes resources, GPU signals, health, configuration, and rollout readiness.
What you will practice
Inspect the serving service; Read gateway logs; List training containers; Inspect a container.
Use the worked examples when needed, then test your understanding without them.
- 01Inspect the serving serviceA serving process has liveness, readiness and dependency state. Inspect the service before restarting it so the intervention addresses a measured condition.Practice
- 02Read gateway logsGateway logs help connect request failures with component state. Keep the request identifier and error category; do not infer root cause from severity alone.Practice
- 03List training containersA container list shows process-level state and names. A running container may still contain an application that has not passed readiness checks.Practice
- 04Inspect a containerContainer inspection reveals the actual image, mounts, limits and network setup. Compare these effective settings with the intended deployment manifest.Practice
- 05Read container resource useResource limits and current use must be interpreted together. Sustained memory close to a hard limit can lead to termination even when the host still has free memory.Practice
- 06Validate compose configurationConfiguration validation catches malformed deployment structure before activation. A syntactically valid Compose file still needs separate readiness and workload checks.Practice
- 07List Kubernetes workloadsPod readiness summarizes whether workloads can accept traffic under their probes. Running phase alone can coexist with zero ready containers.Practice
- 08Describe a serving podPod description brings together events, scheduling and container state. Use the reported reason to choose a focused investigation.Practice
- 09Read 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
- 10Inspect pod resourcesResource 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.Practice
- 11Review 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
- 12Inspect 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
- 13Match model memory to GPUServing memory includes weights, cache and working buffers. Compare their combined demand with available memory, not only the artifact size.Practice
- 14Read readiness evidenceReadiness should cover the dependencies needed for useful work. A process can listen on a port while a required index or model remains unavailable.Practice
- 15Inspect service dependenciesDependency checks identify what a service needs to work. Prefer repairing the failing dependency over restarting healthy callers without evidence.Practice
- 16Prepare a rollout reviewA rollout review combines the diff, compatibility, capacity, readiness and rollback. Explicitly record untested conditions rather than converting them into a pass.Practice
- 17Serving and resources checkpointServing acceptance requires the actual running version and successful readiness under the intended workload. Do not sign off from configuration alone.Practice