pioneer-hash commented on issue #403: URL: https://github.com/apache/apisix-ingress-controller/issues/403#issuecomment-825416179
> > > @pioneer-hash Is there an `ApisixRoute` object named as `web2` in the default namespace, the error log might be occurred due to that resource. > > > > > > No, That's not the name , route name is test-cookie-222 > > ``` > > [root@host-172-21-9-35 CRD]# kubectl get ar -n gray-ns > > NAME AGE > > test-cookie-222 144m > > ``` > > > > > > This is route.yaml > > ```yaml > > apiVersion: apisix.apache.org/v2alpha1 > > kind: ApisixRoute > > metadata: > > name: test-cookie-222 > > namespace: gray-ns > > spec: > > http: > > - name: rule1 > > priority: 1 > > match: > > paths: > > - /* > > backends: > > - serviceName: web3 > > servicePort: 81 > > weight: 70 > > - serviceName: web2 > > servicePort: 81 > > weight: 30 > > - name: rule2 > > priority: 0 > > match: > > paths: > > - /* > > exprs: > > - subject: > > scope: Cookie > > name: name > > op: Equal > > value: zhangsan > > - subject: > > scope: Header > > name: name > > op: NotEqual > > value: lisi > > > > backend: > > serviceName: web2 > > servicePort: 81 > > ``` > > Sorry, my bad, I mean the `ApisixUpstream`. I found that the upstream of Web2 was referenced first in the route.yaml configuration and then execute apply -f upstream.yaml Its success. Is it because you have to do it in order？ -- 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. For queries about this service, please contact Infrastructure at: [email protected]
