After applying a Service for the tax-assessor API, kubectl reports no endpoints even though Pods are running. What binding mechanism should the team verify first?
Select an answer to reveal the explanation.
Short Explanation
Services and Deployments find Pods by label selectors, like matching luggage tags—not by hoping the Pod’s name equals the Service name. Mismatched labels are the classic empty-endpoints surprise.
Full Explanation
Kubernetes controllers and Services select Pods with label selectors. If Service selectors do not match Pod labels, endpoints stay empty even when Pods are Running. Name equality between Service and Pod is not the binding model. Labels also support targeting such as OKE node-pool labels. Image deletion and “no namespaces” are red herrings for this symptom.