An administrator is upgrading an existing VMware vSphere Kubernetes Service (VKS) cluster and receives the...

VCF 9.0 documentation emphasizes that administrators commonly work withmultiple Kubernetes contexts(Supervisor context, namespace contexts, and workload-cluster contexts), and mustswitch to the correct contextbefore running kubectl commands against a specific target. It explains that when you connect, the CLI generates and appends contexts into the kubeconfig, and you thenswitch between contextsusing the context-management commands (for example, listing contexts and using a specific context).

It further describes the correct pattern for interacting with a VKS workload cluster: obtain or generate theworkload-cluster kubeconfig/context, then run kubectl (such as kubectl get nodes) against that workload cluster context.

In this scenario, the errors appear while attempting cluster operations after a Supervisor update, which strongly indicates kubectl is not pointed at the intended endpoint/context (for example, still using a Supervisor/namespace context or an incorrect kubeconfig entry). Because VCF explicitly calls out context creation andcontext switchingas required steps to target the correct cluster, the most verified cause among the options isbeing in the wrong cluster context.