Answer-first summary for fast verification
Answer: Install and configure Config Connector in Google Kubernetes Engine (GKE).
To manage infrastructure as code (IaC) in a GitOps methodology within Google Kubernetes Engine (GKE) and ensure periodic reconciliation to avoid configuration drift, the recommended approach is to use Config Connector. Config Connector is a Kubernetes add-on that allows you to manage Google Cloud resources through Kubernetes. It enables you to create, update, and delete Google Cloud resources by using Kubernetes manifests, which aligns with the GitOps methodology by treating infrastructure as code that can be versioned and managed in a Git repository. Config Connector periodically reconciles the actual state of your Google Cloud resources with your desired state, thus preventing configuration drift. Option A is the correct choice because it directly addresses the requirement to follow Google-recommended practices for managing infrastructure as code within GKE. Options B, C, and D involve using Terraform, which, while a valid tool for IaC, does not inherently provide the periodic reconciliation feature that Config Connector offers within the GKE environment.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
Your company uses Google Kubernetes Engine (GKE) to run applications deployed via GitOps. Developers often provision cloud resources for their applications. You need to enable developers to manage infrastructure as code while adhering to Google's best practices, including periodic reconciliation to prevent configuration drift. What is the recommended approach?
A
Install and configure Config Connector in Google Kubernetes Engine (GKE).
B
Configure Cloud Build with a Terraform builder to execute terraform plan and terraform apply commands.
C
Create a Pod resource with a Terraform docker image to execute terraform plan and terraform apply commands.
D
Create a Job resource with a Terraform docker image to execute terraform plan and terraform apply commands.
No comments yet.