Skip to the content
Know your tech before you buy it. Makers: get listed from $49/mo

Google Config Sync

docs.cloud.google.com

  • Free plan
  • Open source
  • Linux
  • Web
  • API
  • Self-hosted

What Google Config Sync is

Google Config Sync automates configuration and policy synchronization across Kubernetes clusters. It continuously checks a source of truth and reconciles cluster state, helping prevent configuration drift. Sources can be Git repositories, OCI images, or Helm charts. Config Sync can apply Policy Controller constraints across registered and connected clusters, and provision namespaces with namespace-scoped policies such as RBAC roles for multi-tenancy. It supports Autopilot and Standard GKE clusters, as well as GKE-attached clusters including EKS and AKS. Before enabling it, clusters must be registered to a fleet. Its architecture uses hosted components in Google Cloud alongside open-source components running on GKE. Config Sync is included with Google Kubernetes Engine, subject to a GKE-supported cluster version and fleet registration. It runs only on x86-based nodes, not Arm nodes. The drift-prevention admission webhook may use high memory and cause out-of-memory errors in clusters with many custom resources. Google support packages include options such as 24/7 coverage, phone support, and access to a technical support manager; customer-owned YAML configuration issues are outside its support scope.

Who it suits

Config Sync suits teams managing Kubernetes configuration and policies across GKE or GKE-attached clusters. It is particularly relevant to teams using GitOps workflows and namespace-scoped controls for multi-tenancy.

Good to know, and what to watch

  • Reconciles cluster state against a source of truth.
  • Accepts Git, OCI image, and Helm chart sources.
  • Supports Autopilot and Standard GKE clusters.
  • Can apply Policy Controller constraints across clusters.
  • Included with Google Kubernetes Engine.
  • Clusters must be registered to a fleet first.
  • Runs only on x86-based nodes, not Arm.
  • Admission webhook can cause memory pressure with many custom resources.
  • Google does not support customer-owned YAML configuration issues.

Config Sync included with GKE

Free

Free plan

Getting started

  1. Use a GKE-supported cluster version
  2. Register the clusters to a fleet
  3. Connect a Git repository, OCI image repository or Helm chart source
  4. Enable Config Sync for the fleet
  5. Configure Policy Controller constraints and namespace policies
  6. Use Workload Identity Federation for GKE when fleet packages require secure Google Cloud access

Limits to check

Config Sync requires fleet registration and a GKE-supported cluster version, and it runs only on x86 nodes. The drift-prevention admission webhook may consume high memory and trigger out-of-memory errors in clusters with many custom resources.

The verdict

Config Sync brings ongoing configuration reconciliation and policy management to Kubernetes clusters. Confirm the fleet, node-architecture, and memory constraints fit your environment before enabling it.

Questions people ask

What does Config Sync cost?

The listed Config Sync plan is included with Google Kubernetes Engine at no cost. It requires a GKE-supported cluster version and fleet registration.

Which deployment targets are supported?

It supports GKE clusters and GKE-attached clusters, including EKS and AKS. Autopilot and Standard GKE modes are supported.

Which configuration sources can it use?

Config Sync synchronizes from Git repositories, OCI images and Helm charts. Listed Git sources include GitHub, GitLab, Bitbucket, Cloud Source Repositories and Secure Source Manager.

Does it enforce policies?

Yes. It applies Policy Controller constraints, supports Rego, admission control, runtime enforcement, policy testing and policy reporting.

Is Config Sync open source?

Its architecture includes hosted components running in Google Cloud and open source components running on the GKE cluster.

What the maker publishes

API and extensibility
RootSync and RepoSync Kubernetes custom resources expose configuration fields such as source type, repository, revision, directory, and authentication. source
Architecture
Config Sync includes hosted components running in Google Cloud and open source components running on the GKE cluster. source
Authentication options
Supported repository authentication includes SSH keys, tokens, Kubernetes service accounts, Google service accounts, and GitHub Apps, with method-specific limitations. source
Automatic reconciliation
It continuously monitors the source of truth and reconciles cluster state to match it, preventing configuration drift. source
CLI tooling
Documentation provides the nomos command-line tool for validation, status inspection, hydration, and troubleshooting. source
Cloud integrations
Google documents integrations with the Google Cloud console, Terraform, Google Cloud CLI, Policy Controller, Workload Identity Federation for GKE, and Cloud Monitoring. source
Cluster modes
Config Sync supports both Autopilot and Standard GKE clusters. source
Company founded
Crunchbase lists Google as founded in 1998. source
Company headquarters
Crunchbase lists Google's headquarters as Mountain View, California, United States. source
Company legal name
Crunchbase identifies the maker's legal name as Google LLC and its parent as Alphabet. source
Company ownership
Crunchbase identifies Google as a subsidiary of Alphabet and a for-profit public company traded as NASDAQ:GOOG. source
Documentation depth
The documentation includes guides, quickstarts, installation instructions, gcloud references, error references, RootSync and RepoSync fields, release notes, training, and troubleshooting. source
Drift prevention limitation
The drift-prevention admission webhook can cause high memory usage and out-of-memory errors in clusters with many custom resources. source
Drift reconciliation
Config Sync continuously compares cluster state with the declared source and reconciles differences automatically. source
Fleet requirement
Clusters must be registered to a fleet before Config Sync can be enabled. source
Fleet requirement
Clusters must be registered to a fleet before Config Sync can be enabled. source
GitOps synchronization
Config Sync automates synchronization of configuration and policies across any number of clusters. source
Go module
pkg.go.dev lists Config Sync version v1.23.3 as an Apache-2.0, tagged, redistributable Go module published March 11, 2026. source
Helm rendering
Config Sync fetches and renders Helm charts and can deploy their resulting resources into a namespace. source
Identity security
Workload Identity Federation for GKE is the recommended way to securely connect to Google Cloud services and is required for fleet packages. source
Independent service description
A UK government G-Cloud service summary describes Config Sync as keeping configuration in version control and automatically applying it consistently across Kubernetes clusters. source
Kustomize support
It automatically renders native Kustomize configurations and Helm references, but excludes custom Kustomize plugins. source
Licence
The open-source Config Sync repository is published under the Apache-2.0 licence. source
Limit: application delivery
Google describes Config Sync as complementary to CI/CD and primarily suited to base-layer resources rather than replacing application deployment systems. source

Checked against the maker's pages on 15 Oct 2026.