-
Hi,
At the moment we are able to solve this by defining multipe HTTPRoute definitions. I.e. a separate definition for OPTION and HEAD requests, a separate definition for POST PUT DELETE and GET requests and so on. By this, we are able to bind the one definition to the external-auth policy but not the other one. Is there another way to do this without ending up in multiple HTTPRoute definitions for one Service? Thanks for you help. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
your current implementation is the current workaround until #4085 is implemented which should allow you to define all rules within a single HTTPRoute and then attach a policy to a rule |
Beta Was this translation helpful? Give feedback.
your current implementation is the current workaround until #4085 is implemented which should allow you to define all rules within a single HTTPRoute and then attach a policy to a rule