Kubernetes Services & Service Discovery — Challenge

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.

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 endpoints lists 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#

1. What did you expect, exactly?
2. What happened instead — the error text, not a paraphrase?
3. Which layer is that error from?
4. What is the smallest command that proves the layer below is fine?