VMware Advanced VMware Cloud Foundation 9.0 vSphere Kubernetes Service 3V0-24.25 Question # 4 Topic 1 Discussion
3V0-24.25 Exam Topic 1 Question 4 Discussion:
Question #: 4
Topic #: 1
An administrator enabled cluster scaling by running kubectl edit deployment and updating the number of replicas from 5 to 10. When the cluster was redeployed with the number of replicas set to 5, what was the result?
A.
The cluster did not have sufficient resources to deploy the requested number of pods.
B.
The autoscaling YAML file was not updated.
C.
The cluster YAML file was not updated to reflect the requested number of pods.
D.
The Supervisor YAML file was not updated to enable autoscaling.
In a vSphere Kubernetes Service (VKS) environment, resource management follows aDeclarative Model. When an administrator uses kubectl edit deployment to manually scale a running workload from 5 to 10 replicas, they are modifying thelive stateof the deployment. However, thesource of truthfor a Tanzu Kubernetes cluster in VCF 9.0 is theCluster YAML specificationmaintained by the Cluster API (CAPI) provider within the Supervisor.
If the administrator redeploys the cluster or if the Supervisor’s controller performs a reconciliation loop, it refers back to the original configuration file. If that cluster YAML file still defines the replica count as 5, the Supervisor will terminate the 5 "extra" pods to match the desired state defined in the configuration. This is a common administrative pitfall; for changes to be persistent across redeployments or updates in VCF 9.0, the underlying manifest (the "Desired State") must be updated. Manually editing the live object only provides a temporary change that will be overwritten during the next synchronization or lifecycle event because the cluster YAML file was not updated to reflect the requested increase.
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