New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Receive Upstream Timeout from IP which not present on k8s #5445
Comments
Hi @ibadullaev-inc4 thanks for reporting! Be sure to check out the docs and the Contributing Guidelines while you wait for a human to take a look at this 🙂 Cheers! |
NGINX Ingress Controller configures upstreams using endpointSlices and only those endpoints that also are 'ready'. Can you help me understand your scenario a bit deeper? If it is a timing issue we recommend using a healthcheck |
Hi, thank you for your response
|
Hi @brianehlert Than you for your previous response Is it not possible to add health check if I don't use Nginx Plus ?
|
Passive health checks are always present. But Active health checks are a capability that is specific to NGINX Plus. By default, NGINX Ingress Controller won't add pods to the service upstream group until the pod reports ready. |
Hello, Yes my deployment is configure with live and read probe
|
The deployment doesn't give us much information to assist with. If a pod of a service no longer exists, it should be removed from the ingress controller upstream group for that service. |
Hi, thank you for fast response
Follow manifest related our service
|
Describe the bug
Hi, we are using VirtualServer CRD for configure route on k8s to send traffic to the upstream backend
After restart upstream server (backend) which has temproary IP address, our nginx ingress continue send traffic to the IP address which is not present yet.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
If uptream IP address not present into endpoints why nginx try to send traffic to non-existent IP
Your environment
DigitalOcean
NGINX
Additional context
Add any other context about the problem here. Any log files you want to share.
Config inside ingress controller
The text was updated successfully, but these errors were encountered: