Explanation
This is because according to VMware documentation , developers can only access Kubernetes storage classes that are mapped from VM Storage Policies. They cannot modify or delete them.

Explanation
This is because according to VMware documentation3, these are two use cases that would require the creation of multiple clusters in a workload domain. Different host CPU types may affect EVC compatibility and performance across clusters4. Bare-Metal vs. virtual workloads may have different storage and network requirements that need separate clusters5.

Explanation
This is because according to VMware documentation , this is the recommended order of upgrading VCF components in a Management Domain. The order ensures that there are no compatibility issues or dependencies between different components.

Explanation
Generate Certificate Signing Requests from SDDC Manager - In order to replace the self-signed certificates with third-party signed certificates, the Certificate Signing Requests (CSRs) need to be generated. This can be done from the SDDC Manager UI.
Create and package the certificates in a domain_name.tar.gz file - After the CSRs are generated, they can be used to obtain third-party signed certificates from a certificate authority. Once the certificates are obtained, they need to be packaged in a domain_name.tar.gz file and uploaded to SDDC Manager.
* Generate Certificate Signing Requests (CSRs) from SDDC Manager for each component that requires a certificate1. You can do this from the SDDC Manager UI or using an API call1.
* Have the CSRs signed by a third-party Certificate Authority of your choice1. You can use any external provider that meets your security policy requirements.
* Create and package the certificates in a domain_name.tar.gz file according to the naming convention and folder structure specified by SDDC Manager . You can use any compression tool that supports gzip format.
* Upload and install the certificates using SDDC Manager UI or API . You can also verify and troubleshoot the certificate installation using SDDC Manager.
https://docs.vmware.com/en/VMware-Cloud-Foundation/4.5/vcf-admin/GUID-80431626-B9CD-4F21-B681-A8

Explanation
According to vSphere with Tanzu Architecture1, a Spherelet is a component that runs as a VIB on all Supervisor Cluster ESXi hosts configured with the vSphere Networking Stack. It enables an ESXi hypervisor to act as a Kubernetes master node or a Kubernetes worker node, depending on the role assigned by the Supervisor Cluster control plane.