Microservices shop, mission 6 of 7
A fixed address
intermediate, about 10 minutes, in the Kubernetes Simulator
Opens once you pass Outbound only.
The briefing
From Tom Okafor, product manager at Larchwood (a fictional company)
Our marketplace partner is wiring catalog into their own load balancer. It can't use our ingress: it wants to send traffic to port 30080 on every one of our nodes, and it needs that port to stay put.
Please make catalog's API answer there, without changing how the frontend talks to catalog today. Their engineers will test from inside the network, the way you can from a frontend pod.
What you'll do
- Port 30080 on every node serves catalog's API
- The frontend still reaches catalog by name
- Bonus star: Leave the catalog Service exactly as it was
The mission checks the cluster, not your keystrokes: any fix that works, passes.
Concepts
NodePort Services
A NodePort Service opens the same port, from 30000–32767, on every node; kube-proxy forwards it to the Service's pods, wherever they run. Set
Read the Kubernetes docsnodePortto choose it, or Kubernetes picks one at random. It also keeps a cluster IP, so pods can still use it by name.
More Microservices shop missions
- 1. Find each other
- 2. Wrong door
- 3. One front door
- 4. Need to know
- 5. Outbound only
- 6. A fixed address
- 7. Moved out