How to fix Service has no endpoints: selector does not match any pods in Kubernetes

What this error means

A Headless Service (with clusterIP: None) provides direct pod IP discovery via DNS (no load balancing). When the Service selector does not match any pods, DNS queries return no endpoints. This breaks stateful applications (StatefulSets, clusters) that rely on headless services for peer discovery.

Typical symptoms

• DNS query returns no A records (nslookup returns SERVFAIL)
• Pod cannot connect to peer pods via service DNS
• StatefulSet pods cannot discover each other
• kubectl get endpoints shows empty endpoint list
• Service selector does not match any running pods
• Pod logs show "connection refused" when connecting to service DNS
• SRV record queries fail for headless service

Common causes

1. Pod labels do not match Service selector (typo, case mismatch)
2. Pods not in Running state or still initializing
3. Pods failing readiness probe and not yet "Ready"
4. Service selector expects non-existent labels
5. Pods in different namespace than Service
6. Port numbers do not match between Service and pod
7. Pods killed or evicted before Service selector evaluated

How to fix "Service has no endpoints: selector does not match any pods"

Advanced notes

Frequently asked questions

What does "Service has no endpoints: selector does not match any pods" mean?

A Headless Service (with clusterIP: None) provides direct pod IP discovery via DNS (no load balancing). When the Service selector does not match any pods, DNS queries return no endpoints. This breaks stateful applications (StatefulSets, clusters) that rely on headless services for peer discovery.

How do I fix "Service has no endpoints: selector does not match any pods"?

Headless Service (clusterIP: None) cannot resolve because no pods match the Service selector. DNS returns no A records, stateful applications cannot discover members.

What causes "Service has no endpoints: selector does not match any pods"?

Pod labels do not match Service selector (typo, case mismatch) Pods not in Running state or still initializing Pods failing readiness probe and not yet "Ready"

Is the "Service has no endpoints: selector does not match any pods" error serious?

Yes. This is a high-severity error that usually blocks work until it is fixed, but the steps above resolve it.

Related errors

• cannot re-use a name that is still in use

  How to fix "cannot re-use a name" in Helm

  LOW

• headless service not found

  How to fix "headless service not found" in Kubernetes

  HIGH

• Error: chart not found

  How to fix "chart not found" in Helm

  LOW

• Pod failed to schedule: node(s) did not match pod hard affinity requirements

  How to fix "Hard affinity not satisfiable" error in Kubernetes

  HIGH

• upstream connect error or disconnect/reset before headers. reset reason: overflow

  How to fix "upstream connect error or disconnect/reset before headers" in Kubernetes

  HIGH

• Waiting for rollout to finish

  How to fix "Waiting for rollout to finish" in Kubernetes

  HIGH

Official resources & further reading

• 📚Kubernetes Official Documentation
• 📖
  Kubernetes API Reference(Official Docs)
• 📖
  Kubernetes Tasks: Run Applications(Official Docs)
• 💬
  Stack Overflow: Kubernetes headless service no endpoints(Stack Overflow)
• 🐙
  Kubernetes GitHub Issues(GitHub)