Bird
0
0

Why might a ClusterIP service fail to route traffic even if pods are running and selectors match?

hard📝 Conceptual Q10 of 15
Kubernetes - Services
Why might a ClusterIP service fail to route traffic even if pods are running and selectors match?
Akube-proxy is not running or misconfigured on nodes
BThe service type must be LoadBalancer for routing
CPods must have hostNetwork enabled for ClusterIP
DClusterIP services require external IPs to function
Step-by-Step Solution
Solution:

  1. Step 1: Identify kube-proxy role in routing

    kube-proxy manages network rules for ClusterIP services; if it is down or misconfigured, routing fails.

  2. Step 2: Check other options for correctness

    Service type LoadBalancer is not required for internal routing, hostNetwork is unrelated, and external IPs are not needed for ClusterIP.

  3. Final Answer:

    kube-proxy is not running or misconfigured on nodes -> Option A

  4. Quick Check:

    kube-proxy must run for ClusterIP routing [OK]
Quick Trick: Ensure kube-proxy runs for ClusterIP routing [OK]
Common Mistakes:
  • Thinking LoadBalancer type is needed
  • Assuming pods need hostNetwork
  • Believing external IPs are required

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Kubernetes Quizzes
Kubernetes Fundamentals - What is Kubernetes - Quiz 2easy Kubernetes Fundamentals - Control plane components (API server, scheduler, controller manager, etcd) - Quiz 13medium Labels and Selectors - Using labels for service routing - Quiz 2easy Pods - Pod lifecycle states - Quiz 9hard ReplicaSets and Deployments - Rolling update strategy - Quiz 3easy ReplicaSets and Deployments - ReplicaSet definition - Quiz 2easy Services - Endpoints and endpoint slices - Quiz 8hard Services - Why Services provide stable networking - Quiz 6medium kubectl Essential Commands - kubectl apply vs create - Quiz 13medium kubectl Essential Commands - kubectl explain for API reference - Quiz 14medium