You are creating a Google Kubernetes Engine (GKE) cluster and run this command: The command fails with the error: You want to resolve the issue. What should you do?

The correct answer is B. Request additional Compute Engine quota in the GCP Console. GKE clusters are built on top of Compute Engine virtual machines. When you run a cluster creation command and hit a quota error, the underlying limit is almost always a Compute Engine quota (e.g., CPUs, in-use IP addresses, or instance count) - not a GKE-specific quota. The fix…

Deploying applications

Question

You are creating a Google Kubernetes Engine (GKE) cluster and run this command:

The command fails with the error:

You want to resolve the issue. What should you do?

Options

ARequest additional GKE quota in the GCP Console.
BRequest additional Compute Engine quota in the GCP Console.
COpen a support case to request additional GKE quota.
DDecouple services in the cluster, and rewrite new clusters to function with fewer cores.

How the community answered

(26 responses)

A
8% (2)
B
73% (19)
C
4% (1)
D
15% (4)

Explanation

GKE clusters are built on top of Compute Engine virtual machines. When you run a cluster creation command and hit a quota error, the underlying limit is almost always a Compute Engine quota (e.g., CPUs, in-use IP addresses, or instance count) - not a GKE-specific quota. The fix is to request additional Compute Engine quota via the GCP Console (B), not GKE quota (A or C). Decoupling services (D) avoids the root cause and may not even be feasible depending on the workload.

Topics

#GKE#Compute Engine#Quota Management#Resource Provisioning

Community Discussion

No community discussion yet for this question.

Full PROFESSIONAL-CLOUD-DEVELOPER Practice