Rudrakh Panigrahi

@arkodg raised API PR to support this in both header and source matches. Thought it might be easier to do so when dealing with scenarios where subset IP CIDRs might...

@arkodg E2E tests in PR #4452 is failing with following reason: ``` 2024-10-16T11:30:45.0052006Z Error: Received unexpected error: 2024-10-16T11:30:45.0055244Z BackendTrafficPolicy.gateway.envoyproxy.io "ratelimit-anded-headers-with-invert" is invalid: spec.rateLimit.global.rules[0].clientSelectors[0].headers[1]: Duplicate value: map[string]interface {}{"name":"x-user-name"} ``` I noticed...

Thanks for confirming, also not sure why we need a status check as `Invert` is an attribute of `HeaderMatch` and cannot be found in `SourceMatch` type after I remove it...

@ashutosh-narkar you are right, we have the `status_on_error` set to `503`. But I was more concerned about handling all OPA errors with a single status. For example, the incorrect path...

@ashutosh-narkar thanks for the pointer, while I have a look at this can you also confirm if the status that the plugin returns can be transparently exposed to envoy as...

/retest

/retest