You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Use EKS
Deploy kube-httpcache, 2 pods minimum
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
The text was updated successfully, but these errors were encountered:
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:
Expected behavior
I would expect to be able to cluster the pods.
Environment:
Configuration
Additional context
The text was updated successfully, but these errors were encountered: