Freedom251 › Infrastructure as Code Tools
Google Config Connector
What Google Config Connector is
Google Config Connector lets you manage Google Cloud resources through the Kubernetes API using YAML or JSON. It covers products including Spanner, Cloud Storage, Access Context Manager, AlloyDB for PostgreSQL, API Gateway and Apigee, and can manage resources at project, folder or organization level. Google documents manual installation, Config Controller and a GKE add-on; manual instructions cover Autopilot and Standard GKE clusters. Namespaced mode is recommended for most manual installations because Google describes it as more scalable and better for permission isolation in multi-tenant setups. IAM controls access, while separate service accounts can be used for namespaces. Policy Controller or Open Policy Agent Gatekeeper can govern resource creation, and Prometheus monitoring is documented. Config Connector is free and open source, with self-hosted execution and state management. The Google Cloud resources it creates still incur pay-as-you-go charges. Import and export support varies by resource type, and some existing resources cannot be acquired.
Who it suits
It suits teams managing Google Cloud infrastructure through Kubernetes workflows and policy-as-code controls. It is also relevant for self-hosted deployments needing project, folder or organization scope.
What it does well
- Kubernetes API management for Google Cloud
- YAML and JSON configuration
- Multiple installation methods
- Namespaced permission isolation
- Policy and Prometheus documentation
What to know first
- Created Google Cloud resources incur costs
- Some resources cannot be acquired
- Export support varies by resource type
- Supports Google Cloud only
Limits
Config Connector has resource-type limits for acquisition and export; DataflowFlexTemplateJob, FirestoreIndex, and IAMServiceAccountKey cannot acquire existing resources. Google Cloud resources created through it incur pay-as-you-go charges.
Plans
| Plan | Billed and limits | Price |
|---|---|---|
| Usage-based Google Cloud resources | Google Cloud resource costs apply; the page states pay-as-you-go billing and does not list a separate Config Connector price. · Costs depend on the resources created · Custom quote available from sales | On request |
As cloud.google.com lists them, read 8 Oct 2026. The maker's own page has the final word.
Getting started
- Visit https://cloud.google.com/config-connector
- Choose manual installation, Config Controller, or the GKE add-on
- Prepare a Google Kubernetes Engine Autopilot or Standard cluster for manual installation
- Configure YAML or JSON resources
- Set IAM permissions and optional namespace service accounts
- Apply policy and monitoring integrations if needed
Verdict
Config Connector provides a Kubernetes-oriented way to define and govern Google Cloud resources. The tool is free, but cloud resources remain billable and import or export coverage is not universal.
Questions
Is Google Config Connector free?
Config Connector is free and open source. The Google Cloud resources it creates are billed separately on a pay-as-you-go basis.
Which clouds does it support?
It supports Google Cloud.
How is configuration written?
Resources can be defined with YAML or JSON and managed through the Kubernetes API.
How can it be installed?
Google documents manual installation, Config Controller, and installation as a GKE add-on.
Can it import existing resources?
Import is supported, but acquisition depends on resource type. DataflowFlexTemplateJob, FirestoreIndex, and IAMServiceAccountKey cannot acquire existing Google Cloud resources.
Does it support policy and drift management?
Yes. It supports policy as code and drift detection, with Policy Controller or Open Policy Agent Gatekeeper documented for governance.
Facts from Google Config Connector's own pages
- Cost model
- The pricing page says Config Connector incurs costs for the Google Cloud resources it creates and points users to Google Cloud pricing for details. · cloud.google.com, 8 Oct 2026
- Deployment
- Manual installation instructions cover Google Kubernetes Engine clusters, including Autopilot and Standard installation steps. · docs.cloud.google.com, 8 Oct 2026
- Import/export limitation
- Not all resources support the export command, and some resource types do not support acquiring existing Google Cloud resources. · docs.cloud.google.com, 8 Oct 2026
- Installation options
- Google documents manual installation, Config Controller, and installation as a GKE add-on. · docs.cloud.google.com, 8 Oct 2026
- Monitoring
- The documentation includes instructions for monitoring Config Connector with Prometheus. · docs.cloud.google.com, 8 Oct 2026
- Namespaced mode
- Google recommends namespaced mode for most manual installations, describing it as more scalable and offering better permission isolation for multi-tenant use cases. · docs.cloud.google.com, 8 Oct 2026
- Policy governance
- Google documents using Policy Controller or Open Policy Agent Gatekeeper policies to govern resource creation with Config Connector. · docs.cloud.google.com, 8 Oct 2026
- Purpose
- Config Connector lets users manage Google Cloud resources, such as Spanner and Cloud Storage, through the Kubernetes API. · docs.cloud.google.com, 8 Oct 2026
- Resource acquisition limit
- The documentation lists DataflowFlexTemplateJob, FirestoreIndex, and IAMServiceAccountKey among resources that cannot acquire existing Google Cloud resources. · docs.cloud.google.com, 8 Oct 2026
- Resource coverage
- It supports resources across Google Cloud products, including Access Context Manager, AlloyDB for PostgreSQL, API Gateway, and Apigee. · docs.cloud.google.com, 8 Oct 2026
- Scope
- Config Connector can manage resources at the project, folder, or organization level. · docs.cloud.google.com, 8 Oct 2026
- Security
- Access can be controlled with IAM permissions, and namespaced installations can use separate service accounts for namespaces. · docs.cloud.google.com, 8 Oct 2026
Where Google Config Connector stands on Freedom251
- Infrastructure as Code Tools#26 of 31