Running one container manually is straightforward; keeping several application copies running across machines takes coordination. Kubernetes schedules containers, replaces failed copies and provides resources for describing how applications should run.
A Pod runs one or more containers together. A Deployment manages copies of an application and their updates. A Service gives clients a way to reach those copies as Pods are replaced. You submit configuration describing the desired result, and controllers keep trying to make the running system match it. Start with these pieces before adding more tools.
Try it in a lab
Use a disposable local cluster to deploy a tiny application, observe its rollout and reach it through a Service. Change a replica count, inspect events, then delete only the exercise namespace.
Check your understanding
Explain which controller recreates a deleted Pod and which resources survive that replacement. Record the cluster and client versions used.
Before you start
Never use an existing production context for a tutorial. Pass an explicit kubeconfig or context and verify the namespace before applying manifests.
Read the official guide
Use the project documentation for version-specific commands and prerequisites. Record the versions and results of your own exercise. This page proposes a learning activity; it does not report a Kubedex test.
This is a newly written study reference at an address from the original Kubedex course outline. The original lesson was not recovered. It does not include course enrolment, progress tracking or a certificate.
Sources & further reading
Spotted something that needs another look?
Help improve this page →