when upgrading ESXi software on Dell EMC PowerEdge servers using SDDC Manager Lifecycle Management (LCM), you must use a Dell EMC customized image that contains drivers for specific hardware components such as storage adapters.
https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.virtualsan.doc/GUID-08911FD3-2462-4C1C-AE81-0D4DBC8F7990.html

This is because according to VMware documentation2, these are some of the components that are configured as part of the Supervisor Cluster control plane after enabling Workload Management on a VMware Cloud Foundation Workload Domain:
Tanzu Kubernetes Grid Service: This service enables you to create and manage Tanzu Kubernetes clusters on vSphere with Tanzu.
Kubernetes Grid Orchestrator: This component manages the lifecycle of Tanzu Kubernetes clusters on vSphere with Tanzu.
Spherelet: This component runs on each ESXi host and acts as a kubelet agent that communicates with the Supervisor Cluster control plane.

Explanation
These are NSX components that are automated during this deployment of an edge cluster in a VMware Cloud Foundation environment according to VMware documentation. Tier-0 and Tier-1 gateway configuration is automated by creating a default Tier-0 gateway with two uplinks and a default Tier-1 gateway with one downlink when deploying an edge cluster. Edge VM deployment is automated by deploying two edge VMs per edge node when deploying an edge cluster. Transport Node Profile configuration is automated by creating a transport node profile with N-VDS settings when deploying an edge cluster.

https://docs.vmware.com/en/VMware-Cloud-Foundation/4.5/vcf-management-domain-design/GUID-11177D00-C8BE-4CEC-B997-659CC03B6D12.html According to the VMware KB article Understand vMotion networking requirements (59232), a successful Long Distance vMotion requires a RTT (round-trip time) latency of 150 milliseconds or less, between hosts. This is the maximum accepted latency supported by vMotion across long distances1