VKS cluster lifecycle is managed using adeclarative API: you usekubectl with a YAML fileto specify the desired state of the cluster (for example: ''how many nodes,'' Kubernetes version, sizing, and storage). After the cluster is created, youupdate the YAMLto update the cluster. This is why the correct operational approach is to modify the cluster manifest (cluster.yaml) rather than deleting and redeploying.

Additionally, VKS uses multiple controller layers, whereCluster APIand theVirtual Machine Serviceare responsible for provisioning and managing the lifecycle of the control plane and worker node VMs that make up the VKS cluster. In other words, when you change the declared state for control plane sizing/replica count in the cluster YAML, the platform reconciles to that new state by adjusting the underlying control plane VMs through the supported controllers, instead of requiring disruptive ''tear down and rebuild'' operations.

So, editing the cluster.yaml to adjust the control plane replica count is the method that matches the documented VKS declarative operations model and controller-driven reconciliation.