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/09/30 06:38:50 UTC
[GitHub] [apisix-ingress-controller] LuChenjing opened a new issue #700: ApisixRoute route still work after deleting AR source
LuChenjing opened a new issue #700:
URL: https://github.com/apache/apisix-ingress-controller/issues/700
Using helm to install apisix and apisix-ingress-controller.
apisix version: image apache/apisix:2.7-alpine
apisix-ingress-controller: image apache/apisix-ingress-controller:1.1.0
Here is the ApisixRoute manifest yaml:
```yaml
apiVersion: apisix.apache.org/v2alpha1
kind: ApisixRoute
metadata:
name: observer-apisixroute
namespace: onest-observer
spec:
http:
- name: prometheus-1
match:
paths:
- /monitor1/*
backend:
serviceName: prometheus-monitoring-1
servicePort: 9090
plugins:
- name: proxy-rewrite
enable: true
config:
regex_uri:
- "^/monitor1/(.*)"
- "/$1"
- name: prometheus-2
match:
paths:
- /monitor2/*
backend:
serviceName: prometheus-monitoring-2
servicePort: 9090
plugins:
- name: proxy-rewrite
enable: true
config:
regex_uri:
- "^/monitor2/(.*)"
- "/$1"
- name: grafana-rule
match:
paths:
- /dashboard/*
backend:
serviceName: grafana-ha-svc
servicePort: 3000
plugins:
- name: proxy-rewrite
enable: true
config:
regex_uri:
- "^/dashboard/(.*)"
- "/$1"
```
**Issue1:** After applying the resource only shown URIS: /monitor1/*:
Able to access prometheus1
**Issue2:** Able to accesser by /monitor2/ but shown the page of prometheus1
**Issue3:** After delete ApisixRoute, still able to access the prometheus1
--
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: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] tao12345666333 commented on issue #700: ApisixRoute route still work after deleting AR source
Posted by GitBox <gi...@apache.org>.
tao12345666333 commented on issue #700:
URL: https://github.com/apache/apisix-ingress-controller/issues/700#issuecomment-941953216
can you provide your apisix routes?
--
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: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] Firgeis commented on issue #700: ApisixRoute route still work after deleting AR source
Posted by GitBox <gi...@apache.org>.
Firgeis commented on issue #700:
URL: https://github.com/apache/apisix-ingress-controller/issues/700#issuecomment-989955628
What might also be related is that admin API calls to route are inconsistent:
--
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: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] gxthrj edited a comment on issue #700: ApisixRoute route still work after deleting AR source
Posted by GitBox <gi...@apache.org>.
gxthrj edited a comment on issue #700:
URL: https://github.com/apache/apisix-ingress-controller/issues/700#issuecomment-941896136
@LuChenjing
I have sorted out your screenshots, the configuration worked as expected, maybe you got it wrong understanding？
1. The configuration paragraph of `prometheus-2` in ApisixRoute resource
```yaml
- name: prometheus-2
match:
paths:
- /monitor2/*
backend:
serviceName: prometheus-monitoring-2
servicePort: 9090
plugins:
- name: proxy-rewrite
enable: true
config:
regex_uri:
- "^/monitor2/(.*)"
- "/$1"
```
2. The Prometheus svc
3. Request to Prometheus-2 directly
4. Request to Proemtheus-2 from APISIX
[**The same result as request to Prometheus-2 directly, which is expected**]
5. But， Request to APISIX by `http://100.71.8.124:30005/api/v1/status/config` , I can not see the configure `/api/*` in `ApisixRoute` manifest yaml. So we can’t tell which upstream the request is sent to, and need you to provide the relevant routing configuration.
--
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: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] tokers commented on issue #700: ApisixRoute route still work after deleting AR source
Posted by GitBox <gi...@apache.org>.
tokers commented on issue #700:
URL: https://github.com/apache/apisix-ingress-controller/issues/700#issuecomment-938311726
> The result of curl the right URL is correct. But browser rewrite to a different URL. For issue2, when I try to access the monitor2 from the browser, it will redirect to `http://**.**.**.**:30005/api/v1/status/config` instead of `http://**.**.**.**:30005/monitor2/api/v1/status/config`, so the result shown incorrect. Is this an issue belongs to proxy-rewrite plugin?
I cannot capture the authentic meaning, and there is no redirect stage from the ApisixRoute you configured.
--
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: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] gxthrj edited a comment on issue #700: ApisixRoute route still work after deleting AR source
Posted by GitBox <gi...@apache.org>.
gxthrj edited a comment on issue #700:
URL: https://github.com/apache/apisix-ingress-controller/issues/700#issuecomment-941896136
@LuChenjing
I have sorted out your screenshots, the configuration worked as expected, can you see if your understanding is wrong？
1. The configuration paragraph of `prometheus-2` in ApisixRoute resource
```yaml
- name: prometheus-2
match:
paths:
- /monitor2/*
backend:
serviceName: prometheus-monitoring-2
servicePort: 9090
plugins:
- name: proxy-rewrite
enable: true
config:
regex_uri:
- "^/monitor2/(.*)"
- "/$1"
```
2. The Prometheus svc
3. Request to Prometheus-2 directly
4. Request to Proemtheus-2 from APISIX
[**The same result as request to Prometheus-2 directly, which is expected**]
5. But， Request to APISIX by `http://100.71.8.124:30005/api/v1/status/config` , I can not see the configure `/api/*` in `ApisixRoute` manifest yaml. So we can’t tell which upstream the request is sent to, and need you to provide the relevant routing configuration.
--
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: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] tokers commented on issue #700: ApisixRoute route still work after deleting AR source
Posted by GitBox <gi...@apache.org>.
tokers commented on issue #700:
URL: https://github.com/apache/apisix-ingress-controller/issues/700#issuecomment-938573315
It seems that the configurations are correct, could you try to access the APISIX admin API and print all routes?
--
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: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] gxthrj commented on issue #700: ApisixRoute route still work after deleting AR source
Posted by GitBox <gi...@apache.org>.
gxthrj commented on issue #700:
URL: https://github.com/apache/apisix-ingress-controller/issues/700#issuecomment-953459182
@LuChenjing Is the status code 302 returned by `http://100.71.8.124:30005/monitor2/` ？
--
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: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] LuChenjing commented on issue #700: ApisixRoute route still work after deleting AR source
Posted by GitBox <gi...@apache.org>.
LuChenjing commented on issue #700:
URL: https://github.com/apache/apisix-ingress-controller/issues/700#issuecomment-952783407
> can you provide your apisix routes?
Hi @tao12345666333 Here is our ApisixRoute manifest yaml:
```yaml
apiVersion: apisix.apache.org/v2alpha1
kind: ApisixRoute
metadata:
name: observer-apisixroute
namespace: onest-observer
spec:
http:
- name: prometheus-1
match:
paths:
- /monitor1/*
backend:
serviceName: prometheus-monitoring-1
servicePort: 9090
plugins:
- name: proxy-rewrite
enable: true
config:
regex_uri:
- "^/monitor1/(.*)"
- "/$1"
- name: prometheus-2
match:
paths:
- /monitor2/*
backend:
serviceName: prometheus-monitoring-2
servicePort: 9090
plugins:
- name: proxy-rewrite
enable: true
config:
regex_uri:
- "^/monitor2/(.*)"
- "/$1"
- name: grafana-rule
match:
paths:
- /dashboard/*
backend:
serviceName: grafana-ha-svc
servicePort: 3000
plugins:
- name: proxy-rewrite
enable: true
config:
regex_uri:
- "^/dashboard/(.*)"
- "/$1"
```
--
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: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] Firgeis commented on issue #700: ApisixRoute route still work after deleting AR source
Posted by GitBox <gi...@apache.org>.
Firgeis commented on issue #700:
URL: https://github.com/apache/apisix-ingress-controller/issues/700#issuecomment-989936435
I am having the same issue, after creating routes by applying an apixisroute CRD then deleting it. CRD is deleted but the routes are still shown in the admin (and they work).
Same case with modifying the routes in the CRD, they don't seem to be applied.
--
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: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] LuChenjing edited a comment on issue #700: ApisixRoute route still work after deleting AR source
Posted by GitBox <gi...@apache.org>.
LuChenjing edited a comment on issue #700:
URL: https://github.com/apache/apisix-ingress-controller/issues/700#issuecomment-932326795
Sure, For
> 1. Issue 1 is a CRD definition problem about the column printer.
> 2. For issue 2, could you paste the request/response details, you can use the curl utility.
> 3. Will try to reproduce the issue 3 on my local.
Sure, for issue2:
I got K8S service for prometheus1,2:
CURL the prometheus 2 with the nodePort service:
CURL the prometheus 2 with the exact apisix route path(**same with nodePort service**):
But not able to access the correct service on browser:
--
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: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] tokers commented on issue #700: ApisixRoute route still work after deleting AR source
Posted by GitBox <gi...@apache.org>.
tokers commented on issue #700:
URL: https://github.com/apache/apisix-ingress-controller/issues/700#issuecomment-931897590
1. Issue 1 is a CRD definition problem about the column printer.
2. For issue 2, could you paste the request/response details, you can use the curl utility.
3. Will try to reproduce the issue 3 on my local.
--
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: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] LuChenjing commented on issue #700: ApisixRoute route still work after deleting AR source
Posted by GitBox <gi...@apache.org>.
LuChenjing commented on issue #700:
URL: https://github.com/apache/apisix-ingress-controller/issues/700#issuecomment-952786407
> @LuChenjing I have sorted out your screenshots, the configuration worked as expected, maybe you got it wrong understanding？
>
> 1. The configuration paragraph of `prometheus-2` in ApisixRoute resource
>
> ```yaml
> - name: prometheus-2
> match:
> paths:
> - /monitor2/*
> backend:
> serviceName: prometheus-monitoring-2
> servicePort: 9090
> plugins:
> - name: proxy-rewrite
> enable: true
> config:
> regex_uri:
> - "^/monitor2/(.*)"
> - "/$1"
> ```
>
> 1. The Prometheus svc
> 
> 2. Request to Prometheus-2 directly
> 
> 3. Request to Proemtheus-2 from APISIX
> _[**The same result as request to Prometheus-2 directly, which is expected**]_
> 
> 4. But， Request to APISIX by `http://100.71.8.124:30005/api/v1/status/config` , I can not see the configure `/api/*` in `ApisixRoute` manifest yaml. So we can’t tell which upstream the request is sent to, and need you to provide the relevant routing configuration.
Hi @gxthrj sorry for this late reply...
For point No.5, I am trying to access prometheus2 by path `/monitor2/`, but the request will direct to `http://100.71.8.124:30005/api/v1/status/config` after accessing `http://100.71.8.124:30005/monitor2/` on Chrome browser, this is the problem.
--
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: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] tokers commented on issue #700: ApisixRoute route still work after deleting AR source
Posted by GitBox <gi...@apache.org>.
tokers commented on issue #700:
URL: https://github.com/apache/apisix-ingress-controller/issues/700#issuecomment-937482347
OK, so the results of curl are correct but the page shown from the browser is wrong? I didn't understand the specific meaning of diagram 2 with its lines.
--
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: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] gxthrj edited a comment on issue #700: ApisixRoute route still work after deleting AR source
Posted by GitBox <gi...@apache.org>.
gxthrj edited a comment on issue #700:
URL: https://github.com/apache/apisix-ingress-controller/issues/700#issuecomment-941896136
--
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: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] juzhiyuan commented on issue #700: ApisixRoute route still work after deleting AR source
Posted by GitBox <gi...@apache.org>.
juzhiyuan commented on issue #700:
URL: https://github.com/apache/apisix-ingress-controller/issues/700#issuecomment-993316381
Hi @LuChenjing, would you please add more information about this case?
--
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: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] gxthrj edited a comment on issue #700: ApisixRoute route still work after deleting AR source
Posted by GitBox <gi...@apache.org>.
gxthrj edited a comment on issue #700:
URL: https://github.com/apache/apisix-ingress-controller/issues/700#issuecomment-941896136
@LuChenjing
I have sorted out your screenshots, the configuration worked as expected, maybe you got it wrong understanding？
1. The configuration paragraph of `prometheus-2` in ApisixRoute resource
```yaml
- name: prometheus-2
match:
paths:
- /monitor2/*
backend:
serviceName: prometheus-monitoring-2
servicePort: 9090
plugins:
- name: proxy-rewrite
enable: true
config:
regex_uri:
- "^/monitor2/(.*)"
- "/$1"
```
2. The Prometheus svc
3. Request to Prometheus-2 directly
4. Request to Proemtheus-2 from APISIX
_[**The same result as request to Prometheus-2 directly, which is expected**]_
5. But， Request to APISIX by `http://100.71.8.124:30005/api/v1/status/config` , I can not see the configure `/api/*` in `ApisixRoute` manifest yaml. So we can’t tell which upstream the request is sent to, and need you to provide the relevant routing configuration.
--
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: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] tao12345666333 commented on issue #700: ApisixRoute route still work after deleting AR source
Posted by GitBox <gi...@apache.org>.
tao12345666333 commented on issue #700:
URL: https://github.com/apache/apisix-ingress-controller/issues/700#issuecomment-941953216
can you provide your apisix routes?
--
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: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] LuChenjing commented on issue #700: ApisixRoute route still work after deleting AR source
Posted by GitBox <gi...@apache.org>.
LuChenjing commented on issue #700:
URL: https://github.com/apache/apisix-ingress-controller/issues/700#issuecomment-938289344
The result of curl the right URL is correct. But browser rewrite to a different URL.
For issue2, when I try to access the monitor2 from the browser, it will redirect to `http://**.**.**.**:30005/api/v1/status/config` instead of `http://**.**.**.**:30005/monitor2/api/v1/status/config`, so the result shown incorrect.
Is this an issue belongs to proxy-rewrite plugin?
--
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: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] gxthrj commented on issue #700: ApisixRoute route still work after deleting AR source
Posted by GitBox <gi...@apache.org>.
gxthrj commented on issue #700:
URL: https://github.com/apache/apisix-ingress-controller/issues/700#issuecomment-941896136
@LuChenjing
I have sorted out your screenshots, the configuration is the same as expected, can you see if your understanding is wrong？
1. The configuration paragraph of `prometheus-2` in ApisixRoute resource
```yaml
- name: prometheus-2
match:
paths:
- /monitor2/*
backend:
serviceName: prometheus-monitoring-2
servicePort: 9090
plugins:
- name: proxy-rewrite
enable: true
config:
regex_uri:
- "^/monitor2/(.*)"
- "/$1"
```
2. The Prometheus svc
3. Request to Prometheus-2 directly
4. Request to Proemtheus-2 from APISIX
[**The same result as request to Prometheus-2 directly, which is expected**]
5. But， Request to APISIX by `http://100.71.8.124:30005/api/v1/status/config` , I can not see the configure `/api/*` in `ApisixRoute` manifest yaml. So we can’t tell which upstream the request is sent to, and need you to provide the relevant routing configuration.
--
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: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] tokers commented on issue #700: ApisixRoute route still work after deleting AR source
Posted by GitBox <gi...@apache.org>.
tokers commented on issue #700:
URL: https://github.com/apache/apisix-ingress-controller/issues/700#issuecomment-937482347
OK, so the results of curl are correct but the page shown from the browser is wrong? I didn't understand the specific meaning of diagram 2 with its lines.
--
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: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] gxthrj commented on issue #700: ApisixRoute route still work after deleting AR source
Posted by GitBox <gi...@apache.org>.
gxthrj commented on issue #700:
URL: https://github.com/apache/apisix-ingress-controller/issues/700#issuecomment-941896136
@LuChenjing
I have sorted out your screenshots, the configuration is the same as expected, can you see if your understanding is wrong？
1. The configuration paragraph of `prometheus-2` in ApisixRoute resource
```yaml
- name: prometheus-2
match:
paths:
- /monitor2/*
backend:
serviceName: prometheus-monitoring-2
servicePort: 9090
plugins:
- name: proxy-rewrite
enable: true
config:
regex_uri:
- "^/monitor2/(.*)"
- "/$1"
```
2. The Prometheus svc
3. Request to Prometheus-2 directly
4. Request to Proemtheus-2 from APISIX
[**The same result as request to Prometheus-2 directly, which is expected**]
5. But， Request to APISIX by `http://100.71.8.124:30005/api/v1/status/config` , I can not see the configure `/api/*` in `ApisixRoute` manifest yaml. So we can’t tell which upstream the request is sent to, and need you to provide the relevant routing configuration.
--
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: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] LuChenjing commented on issue #700: ApisixRoute route still work after deleting AR source
Posted by GitBox <gi...@apache.org>.
LuChenjing commented on issue #700:
URL: https://github.com/apache/apisix-ingress-controller/issues/700#issuecomment-938386062
Here's the background. I am trying to use ApisixRoute to be the entrance of our local services,
as need to work in private cloud and there is no DNS server. So I want to access different services by different path, can check the detail `ApisixRoute manifest yaml` above.
I used the `proxy-rewrite plugin`, but met the issue2(cannot access No.2 prometheus by accessing path`/monitor2`), am i doing wrong configuration?
--
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: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] LuChenjing commented on issue #700: ApisixRoute route still work after deleting AR source
Posted by GitBox <gi...@apache.org>.
LuChenjing commented on issue #700:
URL: https://github.com/apache/apisix-ingress-controller/issues/700#issuecomment-932326795
Sure, For
> 1. Issue 1 is a CRD definition problem about the column printer.
> 2. For issue 2, could you paste the request/response details, you can use the curl utility.
> 3. Will try to reproduce the issue 3 on my local.
Sure, for issue2:
I got K8S service for prometheus1,2:
CURL the prometheus 2 with the nodePort service:
CURL the prometheus 2 with the exact apisix route path(**same with nodePort service**):
But not able to access the correct service on browser:
--
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: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org