06 · KubernetesLab 33 / 59
Challengekubernetes
Kubernetes Services & Service Discovery — Challenge
Give disposable Pods a stable address, then break the selector and watch the endpoints empty.
- Time
- 45 min
- Level
- Beginner
- Objectives
- 4 objectives
- Cost
- Free
Where this fits in the platform
Already built
This lab adds
- A stable name and address in front of moving pods
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 why a Pod IP is never a valid target
- Read `kubectl get endpoints` as the first debugging step
- Reach a Service by DNS name from inside the cluster
Cost — Free
— runs on kind, minikube or Docker Desktop.
The goal#
Achieve the same outcome as Kubernetes Services & Service Discovery, from an empty starting point, without the steps.
Pods are replaced constantly and get a new IP every time. Nothing can hold a Pod IP.
A Service is the answer, and kubectl get endpoints is the single most useful command when one does not work.
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 ClusterIP Service routes traffic to three Pods, verified by repeated requests hitting different ones.
kubectl get endpointslists three addresses.- Another Pod reaches the Service by name, not by IP.
- You can make the endpoint list empty in two different ways, and explain each.
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 33 of 59 on the project path