Three shop Pods are Running and Ready, yet wget http://shop from the client Pod gets a connection refused.
About this scenario
Three shop Pods are Running and Ready, yet wget http://shop from the client Pod gets a connection refused.
When a Service answers with nothing, the first thing to check is whether it has endpoints, and why not.
Objectives
- The shop Service has 3 ready endpoints
- The client Pod gets an answer from http://shop
What you'll practice
- A Service with a selector that matches nothing has no endpoints, and connections to it are refused.
- The EndpointSlice lists exactly the Pods a Service sends traffic to. Check it first.
- Labels and selectors are the only link between Services and Pods.
How the playground works
The cluster runs entirely in your browser: a simulated API server, scheduler, kubelets and controllers, with virtual nodes in three zones. kubectl output follows the real formats, errors use the real messages, and the add-ons (CSI storage, Traefik, Envoy Gateway, cert-manager, Flux, Argo CD) behave like their real counterparts for the common paths. It's a simulation, so some behavior is simplified. Your progress is saved in this browser.