OptionalattachmentOptionalcpuIf the VMI requires dedicated CPUs, this field will hold the dedicated CPU set on the target node
OptionaldirectThe list of ports opened for live migration on the destination node
OptionaldomainThe Target Node has seen the Domain Start Event
OptionaldomainThe name of the domain on the source libvirt domain
OptionaldomainNamespace used in the name of the source libvirt domain. Can be used to find and modify paths in the domain
OptionaldomainThe timestamp at which the target node detects the domain is active
OptionalmigrationThe Source VirtualMachineInstanceMigration object associated with this migration
OptionalnodeThe source node that the VMI originated on
OptionalnodeThe address of the target node to use for the migration
OptionalnodeIf the VMI requires dedicated CPUs, this field will hold the numa topology on the target node
OptionalpersistentIf the VMI being migrated uses persistent features (backend-storage), its source PVC name is saved here
OptionalpodThe source pod that the VMI is originated on
OptionalselinuxSELinuxContext is the actual SELinux context of the pod
OptionalsyncThe ip address/fqdn:port combination to use to synchronize the VMI with the target.
OptionalvirtualVirtualMachineInstanceUID is the UID of the target virtual machine instance
The UID of the target attachment pod for hotplug volumes