Description

Deployed OSC 1.7.0 on an on-prem baremetal cluster. Configured peer-pods for Azure provider. Pod VM image creation doesn't work as the OSC operator detects the bare metal provider as libvirt and starts creating pod VM image for libvirt

Steps to reproduce

1. Setup OCP cluster on baremetal
2. Setup OSC 1.7.0
3. Create peer-pods-cm and peer-pods-secret for Azure
4. Create KataConfig

Expected Result

1. podvm image created for Azure
2. peer-pod configured for Azure

Actual result

Operator starts creating libvirt image

Impact

Prevents customer from using pod VM in hybrid cloud deployments and cloud-bursting scenarios

Env

<Where was the bug found, i.e. OCP build, operator build, kata-containers build, cluster infra, test case id>

Additional helpful info

<logs, screenshot, doc links, etc.>