Your company runs applications in Google Kubernetes Engine (GKE) that are deployed following a GitOps methodology. Application developers frequently create cloud resources to support their application

Question

Options

• AInstall and configure Config Connector in Google Kubernetes Engine (GKE).
• BConfigure Cloud Build with a Terraform builder to execute terraform plan and terraform apply
• CCreate a Pod resource with a Terraform docker image to execute terraform plan and terraform
• DCreate a Job resource with a Terraform docker image to execute terraform plan and terraform

• A
  71% (27)
• B
  16% (6)
• C
  5% (2)
• D
  8% (3)

Explanation

Config Connector is a Google-maintained Kubernetes add-on that lets developers manage Google Cloud resources (Cloud SQL, GCS, Pub/Sub, etc.) using Kubernetes CRDs stored in Git. It continuously reconciles the declared desired state against actual GCP resource state, directly preventing configuration drift - which is the core requirement. This fits naturally into a GitOps workflow since all resource definitions live in source control. Options B, C, and D all involve Terraform but require external triggers or one-time Jobs; none provide the continuous, periodic reconciliation that Config Connector delivers natively.

No community discussion yet for this question.