[Bug]: Tag based routing uses OR logic for tag matching #17081
Description
What happened?
I have defined model deployments with a tag system for region routing. These contain two keys each, ["region", "country_code"] e.g. ["eu", "de"].
Sending both tags in the request, the request is not reliably sent to the expected deployment that would match both tags. Instead, it is matching any deployment with either tag. Therefore, I need to send only the country code (second tag) to ensure we hit the right deployment.
I was expecting tag based routing to respect each tag defined in the request. This OR logic is not documented either.
Relevant log output
Are you a ML Ops Team?
No
What LiteLLM version are you on ?
v1.80.0
Twitter / LinkedIn details
No response