Fix a Service With No Endpoints

easy 10 XP ~6 minHands-on lab

Clients of the payouts Service in namespace risk get connection errors, although the payouts Deployment reports all replicas ready. A payouts-canary Deployment is being tested next to it and must not receive regular traffic yet.

Task

  • Service payouts in namespace risk routes to every ready Pod of Deployment payouts.
  • It does not route to any Pod of Deployment payouts-canary, or to any other Pod.
  • Keep the Service's name, type and ports as they are.
  • Do not change the Deployments payouts and payouts-canary (both keep running with their current Pod labels).

A practice cluster is running on this machine: start with kubectl get endpointslices -n risk.

About this machine

Ubuntu 24.04 with a private practice cluster: a real Kubernetes API server, scheduler and controllers, and three nodes (controlplane, node01, node02). Containers are simulated, so images never download and kubectl logs/exec are not available. k is an alias for kubectl, with completion. The grader checks the cluster's final state, not the commands you typed.

TerminalNot started

Your machine is ready to start

Create a free account to open a machine and get graded.