An organization has standardized on the following configurations:vSphere Kubernetes Services upgrade is separate from vCenter...

In VMware Cloud Foundation (VCF) 9.0, Supervisor Services allow administrators to extend the capabilities of the vSphere Supervisor by deploying integrated components such as Harbor, Velero, or custom operators. To satisfy the requirement where the vSphere Kubernetes Service (VKS) upgrade must remain independent of the vCenter Server’s release cycle, the " Asynchronous " delivery model must be utilized. This model decouples the lifecycle of the service from the core vSphere platform, allowing for more frequent security patches and feature updates without requiring a full infrastructure upgrade.

When an administrator registers a new Supervisor Service, they must choose the source and lifecycle path. Selecting Asynchronous Private is the specific recommendation for organizations that utilize a private container registry. The " Asynchronous " aspect ensures the service is not tied to the vCenter versioning, while the " Private " designation allows the administrator to specify an internal registry URL and credentials. This configuration ensures that the Supervisor pulls the necessary OCI images and configuration manifests from the local, secure repository rather than the default VMware public registry. This approach is fundamental in VCF 9.0 for maintaining high-security standards (air-gapped or restricted egress environments) while providing the flexibility for DevOps teams to manage the versioning of their Kubernetes-integrated services independently of the underlying SDDC management components.