PREQUEL-2025-0103
Ingress Nginx Backend Service Has No Active EndpointsMediumImpact: 4/10Mitigation: 5/10
PREQUEL-2025-0103View on GitHub
Description
The ingress-nginx controller has detected that a service does not have any active endpoints.
This typically happens when the service selector does not match any pods or the pods are not in a ready state.
The controller logs a warning message indicating that the service does not have any active endpoints.
Cause
- The service selector does not match any pods.
- The pods are not in a ready state.
- The pods are not scheduled or are in a crash loop.
Mitigation
- Check the service selector to ensure it matches the pods.
- Verify the pods are in a ready state.
- Check the pod logs for any errors or issues.
- Ensure the pods are scheduled and not in a crash loop.