Tanc010
Tanc010
**Describe the bug** A clear and concise description of what the bug is.  **To Reproduce** Steps to reproduce the behavior. **Expected behavior** A clear and concise description of what...
### 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...
request help: 如果service包含多个端口,但是apisixroute的backends并没有指定该service的全部端口时,apisixupstream会出现NotFound的报错
### Issue description  参考上面的代码,如果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  上面的apisixupstream已经删除,但是仍然在执行删除并且删除失败  这里的逻辑是对于删除事件如果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  我发现controller会间隔一段时间做一次全局的sync,每次sync都会作为Add事件最终执行etcd的create,这样就会出错。  上面是定时做全局的sync  上面会将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):...