Update VM instead of VMI when exposing service objects

Signed-off-by: Anish Bista <[email protected]>

docs/network/service_objects.md

@@ -84,6 +84,15 @@ port inside the cluster network:
 
 ## Expose VirtualMachineInstance as a NodePort Service
 
+To expose a VirtualMachineInstance via a NodePort service, you must ensure that the VirtualMachine (VM) resource includes the proper labels in the template section. This is crucial to allow the service to correctly associate with the VM's underlying pod.
+
+```yaml
+template:
+  metadata:
+    labels:
+      kubevirt.io/domain: "__VM_NAME__"
+      vmName: "__VM_NAME__"
+```
 Expose the SSH port (22) of a VirtualMachineInstance running on KubeVirt
 by creating a `NodePort` service:
 
@@ -101,7 +110,7 @@ spec:
     protocol: TCP
     targetPort: 22
   selector:
-    special: key
+    vmName: "__VM_NAME__"
   type: NodePort
 ```