Bird
0
0

You created a Service but clients cannot reach the pods. What is a common mistake causing this?

medium📝 Troubleshoot Q6 of 15
Kubernetes - Services
You created a Service but clients cannot reach the pods. What is a common mistake causing this?
AThe Service has no ports defined
BThe Service selector labels do not match pod labels
CThe pods are running on different nodes
DThe Service type is set to ClusterIP
Step-by-Step Solution
Solution:

  1. Step 1: Check Service selector and pod labels

    If the selector labels do not match pod labels, the Service cannot route traffic to pods.

  2. Step 2: Understand impact on connectivity

    Without matching labels, the Service has no endpoints, so clients cannot connect.

  3. Final Answer:

    The Service selector labels do not match pod labels -> Option B

  4. Quick Check:

    Selector mismatch blocks traffic [OK]
Quick Trick: Match Service selector labels with pod labels [OK]
Common Mistakes:
  • Ignoring label mismatches
  • Thinking ClusterIP blocks connectivity
  • Assuming node location affects Service routing

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Kubernetes Quizzes
Kubernetes Fundamentals - Setting up a local cluster (minikube, kind) - Quiz 15hard Namespaces - Switching namespace context - Quiz 8hard Namespaces - Resource quotas per namespace - Quiz 2easy Pods - Sidecar container pattern - Quiz 12easy Pods - Creating Pods with kubectl - Quiz 5medium ReplicaSets and Deployments - Desired replicas vs actual replicas - Quiz 3easy ReplicaSets and Deployments - Rolling update strategy - Quiz 3easy ReplicaSets and Deployments - ReplicaSet definition - Quiz 4medium kubectl Essential Commands - kubectl apply vs create - Quiz 12easy kubectl Essential Commands - Why kubectl mastery matters - Quiz 11easy