yai-dev opened a new issue, #2086:
URL: https://github.com/apache/apisix-ingress-controller/issues/2086
### Current Behavior
When there is no defined LoadBalancer resource object in the cluster, the
ingress controller consistently attempts to obtain the LoadBalancer object, and
continuous print error logs.
### Expected Behavior
The error message need to pe suppressed and should not be continuously print
when LoadBalancer object has not found. Cause there has some scenes, APISIX
will working on NodePort mode and manually controls Load Balancer listeners on
cloud.
### Error Logs
`error ingress/ingress.go:472 failed to get APISIX gateway external
IPs {"error": "resource name may not be empty"}`
### Steps to Reproduce
1. Install APISIX on cluster
2. Do not create any LoadBalancer object
3. Make APISIX Gateway service working on NodePort mode
4. Create Ingress object with APISIX Ingress annotation
### Environment
- APISIX Ingress controller version: 1.6.0
- Kubernetes cluster version: v1.23.8
--
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]
