An engineering team already runs Google Kubernetes Engine and wants to create and reconcile Google Cloud resources, such as Pub/Sub topics and Cloud Storage buckets, by applying Kubernetes manifests with kubectl so that the cluster continuously keeps those resources in the declared state. Which tool is designed for this approach?
- AConfig Connector, because it represents Google Cloud resources as Kubernetes custom resources and reconciles them from applied manifests. Correct
- BHelm, because its release controller turns chart templates into live Google Cloud buckets and topics and reconciles them on drift.
- CTerraform, because kubectl apply invokes the Terraform provider inside the cluster to keep Google Cloud resources reconciled.
- DGemini Cloud Assist, because it watches the cluster and reissues API calls whenever a Google Cloud resource drifts from the manifest.
Why A is correct: Config Connector installs custom resource definitions so Google Cloud services appear as Kubernetes objects, and its controllers continuously reconcile the actual resources to match the manifests applied to the cluster.
Why B is wrong: Helm templates and installs Kubernetes manifests as releases, but it neither models Google Cloud resources as custom resources nor runs controllers that reconcile buckets or topics against drift.
Why C is wrong: Terraform can create the same resources, but it runs as its own CLI against a state file and is not driven by kubectl apply or a reconciling controller living inside the cluster.
Why D is wrong: Gemini Cloud Assist provides AI-assisted help and recommendations, so it does not act as a Kubernetes controller and does not reconcile applied manifests into live Google Cloud resources.