VCF 9.0 documentation explicitly indicates thatvCenter upgrades and the Supervisor/cluster (Workload Management) upgrade are distinct, noting that “if you have only upgraded vCenter and not the cluster” then DevOps engineers have reduced permissions until the cluster is upgraded. This supports the stated standard that VKS/Workload Management lifecycle can be treated separately from vCenter. For the private registry requirement, VCF 9.0 provides an operational mechanism to authenticate and pull artifacts from private registries: “Registry secrets allow package and repository consumers to authenticate to and pull images from private registries,” implemented via a standard Kubernetes Secret of type kubernetes.io/dockerconfigjson.
Taken together, the standard implies (1)asynchronoushandling (separate lifecycle from vCenter) and (2)privatesourcing (images pulled from an internal registry with registry secrets). Therefore, selectingAsynchronous Privatebest matches both requirements in a single configuration choice, aligning with the documented separation of upgrades and the documented need to use authenticated access to private registries.
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit