DGolubets opened a new issue, #2202:
URL: https://github.com/apache/apisix-ingress-controller/issues/2202
### Issue description
I get lots of logs, like these:
```
2024-04-04T22:48:23+08:00 warn apisix/cluster.go:1164 upstream not
found {"id": "1a9104d9", "url":
"http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/upstreams/1a9104d9";,
"cluster": "default"}
2024-04-04T22:48:24+08:00 warn apisix/cluster.go:1164 upstream not
found {"id": "1a9104d9", "url":
"http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/upstreams/1a9104d9";,
"cluster": "default"}
2024-04-04T23:18:11+08:00 warn apisix/cluster.go:1164 upstream not
found {"id": "1a9104d9", "url":
"http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/upstreams/1a9104d9";,
"cluster": "default"}
```
I'm trying to understand why.
I don't have any upstream resources in k8s, but I have routes.
Those routes have created 2 upstreams which I can see in the dashboard, but
they have different IDs to what I see in the logs.
So my question narrows down to: why does the ingress controller keep looking
for the upstream "1a9104d9" and where does it get this id number from?
### Environment
- your apisix-ingress-controller version (output of
apisix-ingress-controller version --long):
- your Kubernetes cluster version (output of kubectl version):
- if you run apisix-ingress-controller in Bare-metal environment, also show
your OS version (uname -a):
--
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]
