Tanc010

Results 5 issues of Tanc010

**Describe the bug** A clear and concise description of what the bug is. ![image](https://github.com/user-attachments/assets/dde99f54-28f3-44f0-9e39-212a07d51868) **To Reproduce** Steps to reproduce the behavior. **Expected behavior** A clear and concise description of what...

bug

### Description // ApisixRouteHTTPBackend represents an HTTP backend (a Kubernetes Service). type ApisixRouteHTTPBackend struct { **// The name (short) of the service, note cross namespace is forbidden,** // so be...

### Issue description ![Image](https://github.com/user-attachments/assets/456e908c-d188-4492-846b-c262a9ccd0c3) 参考上面的代码,如果apisixroute没有referencing service的某些端口,则会报错“upstream doesn't exist. It will be created after ApisixRoute is created referencing it”。 ### Environment - your apisix-ingress-controller version (output of apisix-ingress-controller version --long): -...

### Issue description ![Image](https://github.com/user-attachments/assets/cb460c20-49d6-402a-b82c-975a93eaf3c3) 上面的apisixupstream已经删除,但是仍然在执行删除并且删除失败 ![Image](https://github.com/user-attachments/assets/333be078-4006-4f62-8f90-33d13300c275) 这里的逻辑是对于删除事件如果cr没有找到,就报错,并且等待下次删除。但是下次肯定还是会删除失败。 ### Environment - your apisix-ingress-controller version (output of apisix-ingress-controller version --long): - your Kubernetes cluster version (output of kubectl version): - if you...

### Issue description ![Image](https://github.com/user-attachments/assets/e2aa9e75-d2c8-4e97-8f02-4ef099aa423a) 我发现controller会间隔一段时间做一次全局的sync,每次sync都会作为Add事件最终执行etcd的create,这样就会出错。 ![Image](https://github.com/user-attachments/assets/aa73de37-8b79-4d57-ba45-017bce7394a2) 上面是定时做全局的sync ![Image](https://github.com/user-attachments/assets/d01a8335-de64-4c6f-8e0a-86d022646738) 上面会将sync作为Add事件 问题:是否可以sync的时候先判断如果etcd中有数据则进行Update而不是Create ### Environment - your apisix-ingress-controller version (output of apisix-ingress-controller version --long): - your Kubernetes cluster version (output of kubectl version):...