DevOps / SRE / Platform Engineer / Stage 9 · Operating a cluster

Follow a pod through scheduling to service discovery

CoreIntermediateDraft, not yet reviewed40 min of activities

"Already know" meets prerequisites. "Not relevant" removes the topic from your total but leaves what builds on it waiting.

Self-check

  • In a kind cluster, deploy two replicas behind a Service. Trace a pod from scheduling to running, find it through the Service's DNS name, and explain why a pod with a wrong label receives no traffic.
  • Evidence to include: Keep the manifests, the pod events from kubectl describe, the Service endpoints, and the label that was wrong.

Try it without the material first, then compare. Save your answer in your notes below. Report a problem with this self-check

Learning activities

4 activities
  • Not done
    Quick Start (opens another site)
    ReadOther sitelink checked 2026-11-21

    Creating and deleting a local cluster with kind, and loading your own images into it.

    4 min
  • Not done
    Pods (opens another site)
    ReadOther sitelink checked 2026-11-21

    What a pod is and why controllers create them.

    13 min
  • Not done
    Kubernetes Scheduler (opens another site)
    ReadOther sitelink checked 2026-11-21

    How the scheduler filters and scores nodes before binding a pod.

    3 min
  • Not done
    Service (opens another site)
    ReadOther sitelink checked 2026-11-21

    Stable endpoints for a changing set of pods, through selectors and DNS.

    20 min

My notes

Saved on this device, synced when signed in
Esc
↑ ↓ to move↵ to open