Impossible to cluster when having readiness gates on port 8080

Describe the bug
When using clustering in combination with Readiness Gates (AWS ALB readiness gates), it is impossible to start the pods, because no endpoint will become available until the endpoints have been populated, but the endpoints will never be populated until the readiness gate passes. This ends up in a loop which never allows a pod to be fully started.

To Reproduce
Steps to reproduce the behavior:

1. Use EKS
2. Deploy kube-httpcache, 2 pods minimum
3. Look at the logs from kube httpcache, an error message like the following one appears:

W0308 14:41:30.853956       1 endpoints_watch.go:66] service 'some_random_service' has no endpoints

Expected behavior
I would expect to be able to cluster the pods.

Environment:

• Kubernetes version: [e.g. 1.26]
• kube-httpcache version: [e.g. v0.7]

Configuration

Additional context

Start by tracing endpoints_watch.go around line 66 and reproduce the two-pod setup on EKS with AWS ALB readiness gates. Compare the endpoint population and readiness behavior, then verify that the pods can start clustering without remaining in the no-endpoints loop.