Bird
0
0

After running kubectl get endpoints myapp, you see an empty list under subsets. What does this indicate about the service's backend pods?

medium📝 Command Output Q5 of 15
Kubernetes - Troubleshooting
After running kubectl get endpoints myapp, you see an empty list under subsets. What does this indicate about the service's backend pods?
ANo pods currently match the service's selector labels
BThe service is of type ExternalName and has no endpoints
CThe pods are running but have failed readiness probes
DThe service is misconfigured with an invalid port
Step-by-Step Solution
Solution:
  1. Step 1: Interpret endpoints output

    An empty subsets list means no IPs or ports are associated with the service.
  2. Step 2: Understand selector impact

    This usually means no pods match the service selector labels, so no endpoints are assigned.
  3. Final Answer:

    No pods currently match the service's selector labels -> Option A
  4. Quick Check:

    Empty endpoints subsets means no matching pods [OK]
Quick Trick: Empty endpoints subsets means no pods match selector [OK]
Common Mistakes:
  • Confusing ExternalName services with regular ClusterIP services
  • Assuming readiness probe failures always remove endpoints
  • Thinking port misconfiguration empties endpoints list

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Kubernetes Quizzes