ikatlinsky commented on issue #1855:
URL:
https://github.com/apache/apisix-ingress-controller/issues/1855#issuecomment-1898087857
This happens because the apisix ingress controller tries to sync Kubernetes
endpoints (services) as upstream. So as long as you have Kubernetes service in
the watched namespace - ingress will try to sync it as an upstream.
Is that an expected behaviour? Are there any ways to disable such a
behaviour?
Example logs
```
2024-01-18T15:35:18+08:00 debug types/types.go:211 sync upstream
nodes change {"cluster": "name=default; base_url=.../apisix/admin",
"upstream_name": "...", "nodes":
[{"host":"10.161.5.20","port":8080,"weight":100}]}
2024-01-18T15:35:18+08:00 debug apisix/upstream.go:43 try to look up
upstream {"name": "...", "url": ".../apisix/admin/upstreams", "cluster":
"default"}
2024-01-18T15:35:18+08:00 debug apisix/upstream.go:59 failed to find
upstream in cache, will try to lookup from APISIX {"name": "...",
"error": "not found"}
2024-01-18T15:35:18+08:00 debug apisix/cluster.go:645 get resource in
cluster {"cluster_name": "default", "name": "upstream", "url":
".../apisix/admin/upstreams/ed2f2b93"}
2024-01-18T15:35:18+08:00 warn apisix/cluster.go:1164 upstream not
found {"id": "ed2f2b93", "url": ".../apisix/admin/upstreams/ed2f2b93",
"cluster": "default"}
```
--
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]
