Interview Kubernetes, Docker, Helm & Podman

How does a Service select its Pods, and what happens if labels do not match?

Kubernetes, Docker, Helm & Podman · Basic level

Answer

A Service selects Pods using labels. If the selector does not match any Pods, the Service still exists, but its EndpointSlice has no usable endpoints, so traffic to that Service fails even though the Pods themselves may be healthy.

Technical explanation

Label discipline is an availability concern: a typo in app labels can create a Service with no endpoints while Deployment replicas look healthy.

Debug Service selection with kubectl get endpointslices, kubectl describe service, and kubectl get pods --show-labels.

Kubernetes resources are declarative API objects; controllers continuously drive actual state toward spec.

The practical interview angle is to connect the concept to reliability: scheduling, healing, scaling, rollout safety, and clear ownership.

Use kubectl get, describe, explain, and -o yaml to move from high-level view to exact spec/status details.

Hands-on example

1. Create a local lab with kind or minikube, then use it to demonstrate: intentionally break a Service selector and observe empty EndpointSlices.

2. Run kubectl get nodes -o wide, kubectl get pods -A, kubectl describe, and kubectl get -o yaml to connect the concept to actual cluster state.

3. Make one intentional change, such as a label change, image update, or replica change, and watch how the control plane reconciles it.

4. Capture the command output and convert it into an interview story: desired state, observed state, failure mode, and fix.

Preparing for an interview?

Check how well your resume matches the role with our free resume checker— match score, ATS check, and the skills you're missing.

More Kubernetes, Docker, Helm & Podman interview questions

← All Kubernetes, Docker, Helm & Podman questions