06 · KubernetesLab 32 / 59
Challengekubernetes
Kubernetes Workloads: Pod, ReplicaSet, Deployment — Challenge
Watch a Deployment create a ReplicaSet create Pods, then delete each in turn and see which come back.
- Time
- 45 min
- Level
- Beginner
- Objectives
- 4 objectives
- Cost
- Free
Where this fits in the platform
This lab adds
- The application as a Deployment that survives a deleted pod
Before you start
You will need
- kind or minikube
- kubectl 1.28+
You do not need these already — the lab environment below provides them.
You will be able to
- Explain the Deployment → ReplicaSet → Pod ownership chain
- Perform a rolling update and roll it back
- Match a selector to labels, and recognise when they do not
Cost — Free
— runs on kind, minikube or Docker Desktop. No cloud account needed.
The goal#
Achieve the same outcome as Kubernetes Workloads: Pod, ReplicaSet, Deployment, from an empty starting point, without the steps.
Ingress, HPA and NetworkPolicy all assume you know what a Pod is and what owns it. This lab builds that, by creating each object and then deleting it to see what the cluster does about it.
Deleting things on purpose is the fastest way to learn what is watching.
Hands-on environment
Run this lab in a real terminal, free and in your browser. The environment is temporary and yours alone — break it as much as you like.
Start the challengeOpens in Killercoda, in a new tab — keep this page open for the steps.
This is the guided lab's environment — the same machine, with its walkthrough on the left. Work from the task above and leave those steps alone until you are done, or you are reading the answers.
Run it on your own machine
Run this lab on your own machine. One command starts the environment, with everything the lab needs already installed:
You will need:
- docker
- kubectl
- kind
git clone https://github.com/EgyKode/EgyKode-lab.git
cd EgyKode-lab
./egykode start k8s
./egykode shellYou need Docker and Git installed. Everything else runs inside the environment. The first start downloads it and takes a few minutes; later starts are seconds.
Not sure what you already have? Run: npm run doctor — it checks and changes nothing.
Anything you tick here is your own record. EgyKode cannot see inside that terminal, so the success criteria stay self-assessed even when the environment checks your work for you.
What must be true when you are done
Step 1 of 3
What must be true when you are done#
- A Deployment with 3 replicas is running, and you can name the ReplicaSet that owns the Pods.
- Deleting a Pod causes a replacement to appear; deleting the Deployment does not.
- A rolling update keeps the service available, and
rollout undoreturns to the previous image. - You can produce a Deployment that creates zero Pods, and explain why.
Rules#
- Do not open the guided lab until you are finished, or until the same problem has held you up for 20 minutes.
- Documentation is allowed. In the job it is the first thing you open.
- Verify every criterion with a command whose output you can read.
If you get stuck#
- What did you expect, exactly?
- What happened instead — the error text, not a paraphrase?
- Which layer is that error from?
- What is the smallest command that proves the layer below is fine?
You are done when
0 of 4
The concept behind it
Next up
Lab 32 of 59 on the project path