sina-devel commented on issue #12704:
URL: https://github.com/apache/apisix/issues/12704#issuecomment-3454412651
This problem also occurs even if I apply the `ApisixGlobalRule` with both
plugins defined in the same manifest, like this:
```
apiVersion: apisix.apache.org/v2
kind: ApisixGlobalRule
metadata:
name: global
namespace: apisix
spec:
plugins:
- name: ip-restriction
enable: true
config:
whitelist:
- ...
- name: real-ip
enable: true
config:
source: http_x_real_ip
```
The controller still creates two separate global rules inside APISIX — one
for `ip-restriction` and one for `real-ip`.
As a result, the execution order follows their creation time.
So `ip-restriction` (created first) runs before `real-ip`.
I’ve confirmed this behavior through the APISIX Dashboard as well:
When creating a single Global Rule that includes both plugins directly in
APISIX Dashboard, the execution order is correct and matches the official
documentation.
But when there are two separate Global Rules, APISIX executes the plugins in
order of the GlobalRule creation timestamps.
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
