VirtualServer support for services/upstreams in foreign namespace

[mkingst]

VS mandates that upstreams must reside in the same namespace as the VS resource itself, creating complexity for multi-tenant environments where namespaces are isolated per tenant.

NIC users operating at scale (e.g., VS and VSRs sitting across multiple namespaces) are experiencing challenges due to the current coupling of VS and VSR CRD's.

Some users want to simplify this by containing all updates within one VS itself, as an option to reducing maintenance overhead.

Requirements and Acceptance Criteria

• Modify VirtualServer to support routing to upstreams/services in different namespaces.
• Ensure backward compatibility for existing VS/VSR configurations.
• Update documentation
• Existing VS/VSR setups remain unaffected.

Tasks:

• Design
• POC

[github-actions]

Hi @mkingst thanks for reporting!

Be sure to check out the docs and the Contributing Guidelines while you wait for a human to take a look at this 🙂

Cheers!