" In the vSphere Client, browse to the vCenter cluster where Workload Management is enabled. Select Configure. Select Supervisor Cluster. Select Image Registry. Click Enable Harbor. Select the Storage Policy for placement of container images. Click OK to complete the process " https://docs.vmware.com/en/VMware-vSphere/7.0/vmware-vsphere-with-tanzu/GUID-AE24CF79-3C74-4CCD-B7C7-757AD082D86A.html

https://docs.vmware.com/en/VMware-Cloud-Foundation/5.0/vcf-design/GUID-2156EC66-BBBB-4197-91AD-660315385D2E.html

The correct tool to use for replacing the vSAN Witness appliance for a VMware Cloud Foundation stretched vSAN cluster is the vSphere Client.  According to the VMware Cloud Foundation documentation 1 , you can replace or change the vSAN witness host for a stretched cluster using the vSphere Client without affecting life cycle operations of SDDC Manager. You need to select a new host to use as the vSAN witness host, claim disks on the new witness host, and review the configuration.

vSphere Update Manager is not the correct tool, because it is used for patching and upgrading ESXi hosts, not for replacing vSAN witness hosts 2

SDDC Manager is not the correct tool, because it does not have a workflow for replacing vSAN witness hosts.  You need to use the vSphere Client for this task 1

vSAN PowerCLI is not the correct tool, because it is a PowerShell module that provides cmdlets for managing and automating vSAN environments, not for replacing vSAN witness hosts 3

References :  1 : Change the vSAN Witness Host in a Stretched Cluster - VMware Docs  2 : Upgrade ESXi Hosts Using vSphere Update Manager - VMware Docs  3 : VMware PowerCLI User’s Guide - VMware Docs

To create a VI workload domain with VMFS on FC storage, the hosts must be commissioned with VMFS on FC as the storage type and must be associated with a vMotion only or vMotion and NFS network pool. https://docs.vmware.com/en/VMware-Cloud-Foundation/5.0/vcf-admin/GUID-4EBF9094-F732-4800-86FF-30C5D88B9758.html

To deploy a VI Workload Domain with VMFS on FC storage, the hosts must be associated with a network pool that contains the vMotion network information. This is because the vMotion network is required for adding a host to the SDDC Manager inventory and for migrating workloads between hosts.

A NFS only network pool, a network pool with vMotion and iSCSI, or an iSCSI only network pool are not valid options for deploying a VI Workload Domain with VMFS on FC storage. These network pools are used for different types of storage, such as NFS, vVols on iSCSI, or vSAN.

The references are:

Network Pool Management , section “Information Required for a Network Pool”

Hosts | VMware Cloud Foundation API Reference Guide APIs , section “The hosts, if intended to be used for VMFS on FC, domain must be associated with either a NFS enabled or vMotion enabled network pool.”