Google Config Connector
cloud.google.com
- Windows
- macOS
- Linux
- API
- Self-hosted
What Google Config Connector is
Google Config Connector lets users manage Google Cloud resources through the Kubernetes API with YAML or JSON. It covers products such as Spanner, Cloud Storage, Access Context Manager, AlloyDB for PostgreSQL, API Gateway, and Apigee, with scope at project, folder, or organization level. Installation choices include manual setup, Config Controller, and a GKE add-on; manual instructions cover Autopilot and Standard clusters. Google recommends namespaced mode for most manual installations because it is described as more scalable and provides better permission isolation for multi-tenant use. IAM controls access, and separate service accounts can be used for namespaces. Policy Controller or Open Policy Agent Gatekeeper can govern resource creation, while Prometheus monitoring is documented. Config Connector is free and open source, but created Google Cloud resources incur pay-as-you-go costs. Import and export support varies by resource type.
Who it suits
It suits teams managing Google Cloud infrastructure through Kubernetes workflows, especially those using policy controls, namespaces, or self-hosted execution. Users should check resource-specific import and acquisition support.
Good to know, and what to watch
- Manages Google Cloud through Kubernetes API
- Supports YAML and JSON configuration
- Offers multiple installation methods
- Includes policy-as-code options
- Supports project, folder, organization scope
- Created resources incur Google Cloud costs
- Import and export support varies
- Some resources cannot acquire existing objects
- Requires Google Cloud deployment
Plans
Every plan and priceUsage-based Google Cloud resources
Open source
The verdict
Config Connector provides a Kubernetes-based way to manage Google Cloud resources with self-hosted state and execution. Its free, open-source software still carries the normal costs of resources it creates, and resource acquisition is not universal.
What the maker publishes
- 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. source
- Deployment
- Manual installation instructions cover Google Kubernetes Engine clusters, including Autopilot and Standard installation steps. source
- Import/export limitation
- Not all resources support the export command, and some resource types do not support acquiring existing Google Cloud resources. source
- Installation options
- Google documents manual installation, Config Controller, and installation as a GKE add-on. source
- Monitoring
- The documentation includes instructions for monitoring Config Connector with Prometheus. source
- 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. source
- Policy governance
- Google documents using Policy Controller or Open Policy Agent Gatekeeper policies to govern resource creation with Config Connector. source
- Purpose
- Config Connector lets users manage Google Cloud resources, such as Spanner and Cloud Storage, through the Kubernetes API. source
- Resource acquisition limit
- The documentation lists DataflowFlexTemplateJob, FirestoreIndex, and IAMServiceAccountKey among resources that cannot acquire existing Google Cloud resources. source
- Resource coverage
- It supports resources across Google Cloud products, including Access Context Manager, AlloyDB for PostgreSQL, API Gateway, and Apigee. source
- Scope
- Config Connector can manage resources at the project, folder, or organization level. source
- Security
- Access can be controlled with IAM permissions, and namespaced installations can use separate service accounts for namespaces. source
Checked against the maker's pages on 8 Oct 2026.