How to set up OpenShift Virtualization ServiceNow CMDB discovery: Deploying an in-cluster MID Server

Stock ServiceNow Kubernetes discovery fails to recognize KubeVirt VMs in OpenShift Virtualization clusters — they appear only as virt-launcher pod rows, never as proper VM configuration items in CMDB. This guide (part 1 of 2) walks through deploying a least-privilege, CA-trusted MID Server inside the OpenShift cluster to fix this. Key steps include creating a dedicated service account bound to the kubevirt.io:view ClusterRole, setting up a MID server user in ServiceNow, building a custom MID server image with an OpenShift service-CA startup hook to avoid TLS trust failures on pod reschedules, and deploying the MID server with pod-mounted token authentication. Common failure modes like CrashLoopBackOff, Down status, and SSLPeerUnverifiedException are covered with fixes. Part 2 builds the custom discovery pattern on this foundation.