Open DGolubets opened 3 months ago
I'm getting the same warnings too
Hello, When I examine the debug mode warnings. I saw that the problem was from Rabbitmq.. It was fixed when I created these upstreams for rabbitmq. But I'm not sure how accurate this approach is. Why is it searching for rabbitmq in an apisix with 0 installations inside?
Actually the endpoint controller in apisix ingress controller tries to look up an upstream resource corresponding to each service endpoint that is created. I am looking into this.
Hi any news on this @Revolyssup ? I just set up apisix and was wondering what upstreams it is referring to. What is that ID it is logging ? My apisix config is empty as of now, so where does the ID come from or is it generated for all endpoints found in the cluster ? Generating warnings for all endpoints which i might not want to handle in apisix seems a bit too much.
Issue description
I get lots of logs, like these:
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