Virtual machines running under OCP Virt commonly do not use the pod network, but communicate via secondary network that directly connects VMs.

This spike is to investigate the potential for supporting OSSM with OCP Virt workloads that communicate via a secondary network. This would enable significantly more OCP Virt workloads to leverage service mesh.

This was discussed in an email thread with phoracek@redhat.com from the OCP Virt team - "OpenShift Virtualization VMs as external VMs" on Sept 16th, and in a follow up meeting, though the outcome was not captured.

This has been raised on Slack and in the Service Mesh AMA a few times:

https://redhat-internal.slack.com/archives/C019EPZ233P/p1752776715506879

This may also relate to UDNs (secondary UDNs): https://issues.redhat.com/browse/OSSM-8216

The outcome of this spike would be a document outlining (if possible) how OSSM can be configured with OCP Virt workloads that use a secondary network.