The
[Google Cloud Platform Terms of Service (section "Discontinuation of Services")](https://docs.cloud.google.com/terms)
defines the deprecation policy that applies to Config Sync.
The [deprecation policy](https://docs.cloud.google.com/terms/deprecation) only applies to the services,
features, or products listed therein.


After a service, feature, or product is officially
deprecated, it continues to be available for at least the period of time defined in the
Terms of Service. After this period of time, the service is scheduled for shutdown.

The following table lists deprecated Config Sync features and
their related shutdown schedules:

| Feature | Deprecated date | Shutdown date | Details |
|---|---|---|---|
| [`spec.git` fields of the `ConfigManagement` API](https://docs.cloud.google.com/kubernetes-engine/config-sync/docs/configmanagement-fields.md.txt#configuration_for_git_repositories) | May 15, 2023 | May, 2024 | The use of `spec.git` fields in a `ConfigManagement` object to manage Git repository configurations is deprecated. The `RootSync` API offers the same functionality, along with additional features. For information about migration, see [Migrate your `ConfigManagement` object](https://docs.cloud.google.com/kubernetes-engine/config-sync/docs/how-to/migrate-multi-repo.md.txt). |