chzhuo opened a new issue #806: URL: https://github.com/apache/apisix-ingress-controller/issues/806
### Issue description  The code show that synced failure Event will be requeue to the `workQueue`. But the Event may be expired while resync ### 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): ### Minimal test code / Steps to reproduce to reproduce this bug by adding two Endpoints to one Deployment 1. Adding Endpoint Event1 arrived 2. Adding Endpoint Event2 arrived 3. The `workQueue` has two events 4. The Event1 sync failure, duo to the network error. and The even1 be requeue 5. The Event2 sync successfully. There are two Nodes in the APISIX Upstream 6. The Event1 sync successfully. There is only one Node in the APISIX Upstream ### Actual result only one Node in the APISIX Upstream ### Error log no error ### Expected result two Nodes in the APISIX Upstream -- 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]
