sebschlue opened a new issue, #2661:
URL: https://github.com/apache/apisix-ingress-controller/issues/2661
### Current Behavior
apisix-ingress-controller:2.0.0-rc5 creates huge amount of connectionss to
apisix admin port until is runs out of ephemeral source ports.
Error message:
```
2025-11-21T13:42:56.336Z ERROR executor client/executor.go:273
failed to run http sync for server {"server":
"http://apisix-admin.ingress-apisix.svc:9180";, "error": "Serve │
│ rAddr: http://apisix-admin.ingress-apisix.svc:9180, Err: HTTP 500:
{\"message\":\"Error: connect EADDRNOTAVAIL 172.20.13.11:9180 - Local
(0.0.0.0:0)\"}"}
```
After 4 hours of uptime, it has created nearly 30K of active connections:
```
# ss | grep -F ':9180' | wc -l
28232
```
All Apisix CR objects get a "unsuccessful sync" status and I need to restart
the ingress-controller pod.
### Expected Behavior
ingress controller should either open, use and close connections or it
should re-use existing pool connections. But it should no simply open new
connectiosn and never close any of them.
### Error Logs
```
2025-11-21T13:42:56.336Z ERROR executor client/executor.go:273
failed to run http sync for server {"server":
"http://apisix-admin.ingress-apisix.svc:9180";, "error": "Serve │
│ rAddr: http://apisix-admin.ingress-apisix.svc:9180, Err: HTTP 500:
{\"message\":\"Error: connect EADDRNOTAVAIL 172.20.13.11:9180 - Local
(0.0.0.0:0)\"}"}
```
### Steps to Reproduce
I have simply deployed version 2.12.2 of the apisix helm chart which
installs apisix version 2.14.1 and apisix-ingress-controller version 2.0.0-rc5.
CRDs have been installed via:
```
kubectl apply --force-conflicts --server-side -f
https://raw.githubusercontent.com/apache/apisix-helm-chart/refs/tags/apisix-2.12.2/charts/apisix-ingress-controller/crds/apisixic-crds.yaml
kubectl apply --force-conflicts --server-side -f
https://raw.githubusercontent.com/apache/apisix-helm-chart/refs/tags/apisix-2.12.2/charts/apisix-ingress-controller/crds/gwapi-crds.yaml
```
### Environment
Runing on EKS 1.32.9
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
