Bird
0
0

If pods inside the cluster cannot reach a ClusterIP service, which of the following is a probable cause?

medium📝 Troubleshoot Q6 of 15
Kubernetes - Services
If pods inside the cluster cannot reach a ClusterIP service, which of the following is a probable cause?
AThe service selector labels do not match any pod labels
BThe service type is incorrectly set to LoadBalancer
CThe service has an external IP assigned
DThe pods are running on nodes outside the cluster
Step-by-Step Solution
Solution:

  1. Step 1: Check service selector

    ClusterIP routes traffic to pods matching the selector labels.

  2. Step 2: Identify mismatch

    If selectors don't match pod labels, no endpoints exist, causing connectivity failure.

  3. Final Answer:

    The service selector labels do not match any pod labels -> Option A

  4. Quick Check:

    Selector must match pod labels [OK]
Quick Trick: Selector labels must match pod labels [OK]
Common Mistakes:
  • Assuming LoadBalancer type causes internal access issues
  • Thinking external IP affects ClusterIP reachability
  • Believing pods outside cluster affect ClusterIP

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