I am helping our integrations team migrate API endpoints from one integrations load-balanced cluster to another. In doing so, they are slowly moving just specific applications. I have created an http forwarding rule to forward certain URIs to the new integration cluster VIP. For some reason, it appears that the policy is somehow be affecting URIs that are not in scope of the rule. I enabled logging on the policy to show me all of the URIs hitting the policy... it appears that only the in-scope ones are hitting it.
That said, certain out of scope API endpoints are returning 404 errors intermittently. When we disassociate the policy from the VIP, there is no issue. I am not sure how the policy could be affecting those URIs (and only sometimes) when they do not appear to be hitting the policy.
I have added a screenshot of the simple policy, the strategy is to execute the first matching rule
That's an interesting one... I don't have an answer for you, but a couple of ideas / troubleshooting tips to hopefully help you further;
Hope any of these are useful 😉