Bird
0
0

A Service selector is defined as app: web, but pods are labeled app=Web. Why does the Service fail to route traffic?

medium📝 Troubleshoot Q6 of 15
Kubernetes - Labels and Selectors
A Service selector is defined as app: web, but pods are labeled app=Web. Why does the Service fail to route traffic?
ALabel keys and values are case-sensitive, so 'web' ≠ 'Web'
BThe selector uses colon syntax, but pods use equal signs
CPods must have multiple labels to match the selector
DService selectors cannot route to pods with labels
Step-by-Step Solution
Solution:

  1. Step 1: Recognize case sensitivity

    Kubernetes label keys and values are case-sensitive.

  2. Step 2: Compare selector and pod labels

    Selector 'app: web' does not match pod label 'app=Web' due to case difference.

  3. Final Answer:

    Label keys and values are case-sensitive, so 'web' ≠ 'Web' -> Option A

  4. Quick Check:

    Case mismatch causes selector to fail [OK]
Quick Trick: Labels are case-sensitive; match exact case [OK]
Common Mistakes:
  • Ignoring case sensitivity in labels
  • Confusing syntax differences with label matching
  • Assuming multiple labels are required

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Kubernetes Quizzes
Kubernetes Fundamentals - Desired state vs actual state reconciliation - Quiz 13medium Kubernetes Fundamentals - Setting up a local cluster (minikube, kind) - Quiz 5medium Labels and Selectors - Adding labels to resources - Quiz 10hard Namespaces - Default namespaces overview - Quiz 7medium ReplicaSets and Deployments - Deployment status and history - Quiz 7medium Services - Headless services concept - Quiz 15hard kubectl Essential Commands - kubectl exec for container access - Quiz 9hard kubectl Essential Commands - kubectl port-forward for local access - Quiz 6medium kubectl Essential Commands - kubectl port-forward for local access - Quiz 10hard kubectl Essential Commands - kubectl get for listing resources - Quiz 5medium