It covers two scenarios, both testing current behavior
1) Two AuthPolicies being attached to GW and HTTPRoute with identical hostname respectively
2) Two AuthPolicies being attached to two HTTPRoutes with identical hostname each
Eye review, execute both tests and make sure they pass.
Note
I will proceed with RateLimitPolicy (RLP) scenarios once this is reviewed so that I can incorporate feedback from this PR there. The 1) scenario for RLP is identical, I will think of using parametrized fixture called policy instead of having two identical tests one using AuthPolicy and other RLP.
The 2) scenario for RLP is slightly different, not sure if it makes sense to try to use the same test for both
Overview
Partially addresses https://github.com/Kuadrant/testsuite/issues/406
It covers two scenarios, both testing current behavior 1) Two AuthPolicies being attached to GW and HTTPRoute with identical hostname respectively 2) Two AuthPolicies being attached to two HTTPRoutes with identical hostname each
For details see https://github.com/Kuadrant/kuadrant-operator/blob/main/doc/auth.md#limitation-multiple-network-resources-with-identical-hostnames
Verification Steps
Eye review, execute both tests and make sure they pass.
Note
I will proceed with RateLimitPolicy (RLP) scenarios once this is reviewed so that I can incorporate feedback from this PR there. The 1) scenario for RLP is identical, I will think of using parametrized fixture called
policy
instead of having two identical tests one using AuthPolicy and other RLP. The 2) scenario for RLP is slightly different, not sure if it makes sense to try to use the same test for both