rezaebrahimzadeh opened a new issue, #12294:
URL: https://github.com/apache/apisix/issues/12294
### Current Behavior
I'm using Apache APISIX in Kubernetes, installed via Helm, with the
following components enabled: etcd, apisix, apisix-ingress-controller, and
dashboard.
The issue occurs when a backend pod is restarted and receives a new IP
address. APISIX sometimes continues to send requests to the *old* pod IP, which
results in request failures (e.g., 502 Bad Gateway or timeout errors).
This doesn't happen every time — it's intermittent. But when it does occur,
restarting the `apisix-ingress-controller` pod resolves the problem, and APISIX
starts using the correct (new) pod IP.
### Expected Behavior
When a backend pod is restarted and its IP changes, APISIX should
automatically detect the change and update the upstream IP to route requests to
the new pod.
### Error Logs
There are no specific APISIX error logs, but I see that requests fail (e.g.
502 or timeout upstreams) when APISIX keeps routing to a deleted pod IP.
### Steps to Reproduce
1. Install APISIX in Kubernetes using the Helm chart (with etcd, apisix,
apisix-ingress-controller, and dashboard enabled).
2. Deploy a backend application with a Kubernetes Service.
3. Create an `ApisixRoute` resource pointing to the backend Service.
4. Restart the backend pod to force an IP change.
5. Occasionally, APISIX continues to send traffic to the old pod IP.
6. Restarting the `apisix-ingress-controller` resolves the issue temporarily.
### Environment
- APISIX version: 3.11.0
- apisix-ingress-controller version: 1.8.0
- Kubernetes version: v1.28
- Installation method: Helm chart (Chart version apisix-2.10.0)
- CRDs used: ApisixRoute
- Backends are standard Kubernetes Services
- All components deployed: etcd, apisix, apisix-ingress-controller, dashboard
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscr...@apisix.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
