Kubernetes - Services
After creating a headless service, DNS queries for the service name return no pod IPs. What is a common misconfiguration causing this?
After creating a headless service, DNS queries for the service name return no pod IPs. What is a common misconfiguration causing this?
medium📝 Troubleshoot Q6 of 15
Step-by-Step Solution
Solution:
Step 1: Check Service selector
The Service selector must match pod labels to associate pods with the Service.Step 2: Impact of selector mismatch
If no pods match the selector, DNS has no pod IPs to return for the headless Service.Step 3: Other options
Service type or namespace mismatch would cause different issues; ports missing does not affect DNS resolution.Final Answer:
The Service selector does not match any pod labels -> Option AQuick Check:
Verify selector labels match pod labels [OK]
Quick Trick: Selector must match pods for DNS to return IPs [OK]
Common Mistakes:
- Ignoring selector label mismatch
- Assuming Service type affects DNS for headless
- Not verifying namespace consistency
Master "Services" in Kubernetes
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Kubernetes Quizzes