You want to enable your running Google Kubernetes Engine cluster to scale as demand for your application changes. What should you do?
A.
Add additional nodes to your Kubernetes Engine cluster using the following command: gcloud container clusters resize CLUSTER_Name ג€" -size 10
B.
Add a tag to the instances in the cluster with the following command: gcloud compute instances add-tags INSTANCE - -tags enable- autoscaling max-nodes-10
C.
Update the existing Kubernetes Engine cluster with the following command: gcloud alpha container clusters update mycluster - -enable- autoscaling - -min-nodes=1 - -max-nodes=10
D.
Create a new Kubernetes Engine cluster with the following command: gcloud alpha container clusters create mycluster - -enable- autoscaling - -min-nodes=1 - -max-nodes=10 and redeploy your application
A is incorrect because there is supposed to be two hypens "--" not one before size (https://cloud.google.com/sdk/gcloud/reference/container/clusters/resize). B is incorrect because it just adds a string to the cluster (https://cloud.google.com/sdk/gcloud/reference/compute/instances/add-tags). "C" is just as wrong as "A" because the documentation says it should be "--max-nodes" followed by "--min-nodes" (https://cloud.google.com/sdk/gcloud/reference/alpha/container/clusters/update), also the alpha command no longer works but it used to and is still up on google docs. This goes for "D" as well but D talks about making another, which doesn't have to be done because one it already up. So the debate is between A and C, and C used to work so C was chosen, although C also has spaces which never worked... So this question is an absolute thug tactic by a Google team to steal from the Google kingdom preventing the establishment of their library by failing people that actually know the science behind the technology. When you see this question at a test center I'd select C.
To enable autoscaling for an existing node pool, run the following command:
gcloud container clusters update cluster-name --enable-autoscaling \
--min-nodes 1 --max-nodes 10 --zone compute-zone --node-pool default-pool
https://cloud.google.com/kubernetes-engine/docs/how-to/cluster-autoscaler
Agreed with C because
Explanation:
Autoscaling in GKE
Kubernetes Engine supports Cluster Autoscaler, which automatically adjusts the size of a node pool based on the resource demands of the workloads.
Enabling autoscaling allows the cluster to add or remove nodes dynamically to handle increased load or scale down during low activity.
Updating the Existing Cluster
The command in option C updates an existing cluster with autoscaling enabled, setting minimum (1) and maximum (10) node limits.
This avoids downtime and does not require recreating the cluster or redeploying applications, ensuring a seamless transition to autoscaling.
Answer should be C. Now alpha command is not needed. seems question is older and now kubernets command is not with alpha.
gcloud container clusters update cluster-name --enable-autoscaling ....
C. Update the existing Kubernetes Engine cluster with the following command: gcloud alpha container clusters update mycluster - -enable- autoscaling - -min-nodes=1 - -max-nodes=10
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
AWS56
Highly Voted 3 years, 11 months agoEroc
Highly Voted 4 years, 2 months agotartar
3 years, 4 months agotartar
3 years, 4 months agosvjl
3 years agopiyu1515
Most Recent 1 day, 5 hours agoanil23
4 months, 3 weeks agoAugustoKras011111
10 months, 1 week agozerg0
11 months agosurajkrishnamurthy
1 year agogonlafer
1 year agomegumin
1 year, 1 month agoAzureDP900
1 year, 2 months agovincy2202
2 years agoBobch
2 years agoTheCloudBoy77
2 years, 1 month ago[Removed]
2 years, 2 months agoExamster1
2 years, 3 months agokopper2019
2 years, 6 months agovictory108
2 years, 7 months ago