An administrator has been tasked to temporarily scale the Control Plane of a VKS cluster with no service disruption. How should the administrator…

Tanzu Kubernetes clusters are managed declaratively. To scale any component, including the control plane, an administrator modifies the cluster's YAML manifest. By changing the value of the spec.topology.controlPlane.replicas field in the TanzuKubernetesCluster object definition and applying the change with kubectl apply, the Cluster API controllers will perform a rolling update. This process adds or removes control plane nodes gracefully to match the desired state without causing service disruption.

B. Deleting and redeploying the cluster is a destructive action that would cause a complete and lengthy service outage, violating the requirement.

C. Namespaces are a mechanism for isolating resources within a cluster; they are not related to the number of control plane nodes.

D. Creating a new cluster is not scaling the existing one. This would require migrating all workloads, which is not what the task asks for.

1. VMware vSphere Documentation, "Managing the Lifecycle of a Tanzu Kubernetes Cluster". The section "Scale a Tanzu Kubernetes Cluster" details the procedure: "To scale a Tanzu Kubernetes cluster, you edit the cluster manifest to change the number of control plane nodes or worker nodes... For example, to scale the control plane, modify the value for replicas under controlPlane."

2. Cluster API Book, "Machine Deployments - Rolling Upgrades". The underlying technology, Cluster API, uses a rolling update strategy by default when the number of replicas in a MachineDeployment (which manages control plane nodes) is changed, ensuring high availability.