Your team is running applications on a Google Kubernetes Engine (GKE) cluster with a private endpoint. You've set up a Cloud Deploy pipeline, but deployments to the GKE cluster are failing. You need t

Question

Options

• AUse VPC Service Controls with Cloud Build Update the Cloud pipeline to use Cloud Build as its
• BCreate a Cloud Build private pool in the default VPC. Use Cloud Build to deploy the applications
• CCreate a Cloud Build private pool that is peered with the same VPC network as your GKE cluster.
• DCreate a custom target in Cloud Deploy Update the deploy pipeline to use the custom target for

• A
  23% (5)
• B
  9% (2)
• C
  59% (13)
• D
  9% (2)

Explanation

A GKE cluster with a private endpoint is only reachable from networks that have private connectivity to the control plane (same VPC or peered). By default, Cloud Deploy uses a public Cloud Build pool, which cannot reach the private endpoint. Creating a Cloud Build private pool that is peered with the same VPC as the GKE cluster, and configuring Cloud Deploy to use this pool as its execution environment, gives the deploy job private network access to the cluster and resolves the deployment failures.

No community discussion yet for this question.