You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@apisix.apache.org by GitBox <gi...@apache.org> on 2021/04/01 03:36:30 UTC
[GitHub] [apisix-ingress-controller] pioneer-hash opened a new issue #326: bug: the priority configuration could not take effect
pioneer-hash opened a new issue #326:
URL: https://github.com/apache/apisix-ingress-controller/issues/326
### Issue description
I configured the priority generic type in route.yaml ,but the generic type is not synchronized to Apisix.
this is my route.yaml
``` yaml
apiVersion: apisix.apache.org/v2alpha1
kind: ApisixRoute
metadata:
name: test-cookie
namespace: default
spec:
http:
- name: rule1
priority: 0
match:
paths:
- /*
backend:
serviceName: web2
servicePort: 80
- name: rule2
priority: 2
match:
paths:
- /*
exprs:
- subject:
scope: Cookie
name: name
op: Equal
value: zhangsan
backend:
serviceName: web1
servicePort: 80
```
When I execute the command kubectl apply-f roue.yaml and check the configuration of apisix, I find that the priority configuration is not successful
### Environment
* your apisix-ingress-controller version (output of `apisix-ingress-controller version --long`);
apisix-ingress-controller version is the current master(2021/3/24 )
apisix image version is 2.4-centos
* 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 the issue
1.
2.
3.
### What's the actual result? (including assertion message & call stack if applicable)
### What's the expected result?
--
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:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] gxthrj closed issue #326: bug: the priority configuration could not take effect
Posted by GitBox <gi...@apache.org>.
gxthrj closed issue #326:
URL: https://github.com/apache/apisix-ingress-controller/issues/326
--
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:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] tokers commented on issue #326: bug: the priority configuration could not take effect
Posted by GitBox <gi...@apache.org>.
tokers commented on issue #326:
URL: https://github.com/apache/apisix-ingress-controller/issues/326#issuecomment-811685352
@pioneer-hash I have committed a PR to solve this problem: https://github.com/apache/apisix-ingress-controller/pull/329.
--
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:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] tokers commented on issue #326: bug: the priority configuration could not take effect
Posted by GitBox <gi...@apache.org>.
tokers commented on issue #326:
URL: https://github.com/apache/apisix-ingress-controller/issues/326#issuecomment-811671782
@pioneer-hash Thanks for your report.
--
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:
users@infra.apache.org