# Managed control plane

> [!CAUTION]
> **Caution:** managed Cloud Service Mesh with the `ISTIOD` control plane implementation is [deprecated](https://docs.cloud.google.com/service-mesh/deprecations.md.txt). You must modernize all managed `ISTIOD` fleets to the `TRAFFIC_DIRECTOR` implementation.

This document explains the architectural differences between the deprecated
`ISTIOD` control plane implementation and Google's modern `TRAFFIC_DIRECTOR`
control plane implementation, and outlines your next steps if your clusters
still use a deprecated control plane.

## Control plane overview

In service meshes, the control plane provides traffic management, proxy
management when the Envoy proxy is in use, and other networking capabilities.

Cloud Service Mesh using Istio APIs on GKE clusters provides
a fully supported implementation of the [Istio APIs](https://docs.cloud.google.com/service-mesh/docs/onboarding/api-support.md.txt).
The APIs are implemented and supported by the fully managed and Cloud Networking
integrated `TRAFFIC_DIRECTOR` control plane. Previously, two additional control
plane implementations were supported:

- The [deprecated](https://docs.cloud.google.com/service-mesh/deprecations.md.txt) **managed `ISTIOD` implementation**, which runs a single-cluster dedicated control plane.
- The [deprecated](https://docs.cloud.google.com/service-mesh/deprecations.md.txt) **in-cluster `ISTIOD` implementation**, which runs customer-managed control plane components inside your cluster.

## Operational characteristics of the `TRAFFIC_DIRECTOR` control plane

Cloud Service Mesh with the `TRAFFIC_DIRECTOR` control plane uses Google Cloud's
managed networking infrastructure rather than per-cluster control plane instances.

The Istio APIs (CRDs) and the xDS configuration sent to Envoy sidecars remain
compatible, but you should expect the following operational characteristics:

- **Policy and service configuration propagation:** When you create new services or update routing and security policies, configuration is validated and propagated across Google Cloud systems before taking effect on sidecars. As a result, initial policy and service propagation takes longer than with in-cluster or `ISTIOD` control planes. For guidance on optimizing deployment workflows, see [Configuration propagation](https://docs.cloud.google.com/service-mesh/docs/operate-and-maintain/scalability-best-practices.md.txt#configuration_propagation).
- **Pod scaling and endpoint updates:** Changes to workload endpoints---such as new Pods created by horizontal Pod autoscaling or Pods restarting with new IP addresses---are propagated directly by the control plane without the latency associated with policy updates. Existing Pods fetching existing configuration start without delay.
- **Multi-cluster endpoint discovery:** In multi-cluster meshes, clusters share their endpoints directly through Google Cloud rather than synchronizing them point-to-point between each combination of clusters. This ensures cross-cluster endpoint state converges more quickly and consistently as your mesh scales.

## How does this affect you?

Your next steps depend on which Cloud Service Mesh
[control plane implementation](https://docs.cloud.google.com/service-mesh/docs/check-control-plane-implementation.md.txt)
your clusters use:

- **Managed control plane (`TRAFFIC_DIRECTOR` implementation):**
  - You are already using the current, globally scalable architecture (whether configured using Istio APIs, Gateway API, or Google Cloud APIs).
  - No action is required.
- **Managed control plane (`ISTIOD` implementation):**
  - This implementation is **[deprecated](https://docs.cloud.google.com/service-mesh/deprecations.md.txt)**.
  - You must take action to inspect your fleet for compatibility blockers, update your configuration, and complete [managed control plane modernization](https://docs.cloud.google.com/service-mesh/docs/modernization.md.txt), or [uninstall managed Cloud Service Mesh](https://docs.cloud.google.com/service-mesh/docs/uninstall-managed.md.txt).
- **In-cluster control plane:**
  - The in-cluster control plane on GKE is **[deprecated](https://docs.cloud.google.com/service-mesh/deprecations.md.txt)**.
  - In-cluster installations cannot be modernized in-place. You must take action to [migrate from in-cluster to the managed control plane on a new cluster](https://docs.cloud.google.com/service-mesh/docs/tutorials/migrate-in-cluster-to-managed-on-new-cluster.md.txt) or [uninstall Cloud Service Mesh](https://docs.cloud.google.com/service-mesh/docs/uninstall.md.txt).

## Control plane modernization for managed Cloud Service Mesh with the ISTIOD implementation

All managed fleets running the deprecated `ISTIOD` implementation must complete
modernization to the `TRAFFIC_DIRECTOR` implementation before the end-of-support
deadline specified in the [deprecation notice](https://docs.cloud.google.com/service-mesh/deprecations.md.txt).
You can modernize your fleet using either **customer-triggered modernization**
(recommended for per-cluster control and staged traffic shifting) or
**Google-driven modernization** (automated rollouts for eligible fleets).

For step-by-step instructions, see
[Managed control plane modernization](https://docs.cloud.google.com/service-mesh/docs/modernization.md.txt).

### Check control plane compatibility

To evaluate your fleet against supported features and identify configuration
blockers before modernization, see:

- [Understanding Cloud Service Mesh compatibility](https://docs.cloud.google.com/service-mesh/docs/migrate/eligibility.md.txt)
- [Configuration updates for modernization](https://docs.cloud.google.com/service-mesh/docs/migrate/modernization-configuration-updates.md.txt)

## Appendix: Control plane rollout and deprecation timeline

The transition from `ISTIOD` control planes to the managed
`TRAFFIC_DIRECTOR` control plane implementation has followed this timeline:

- [**May 23, 2024**](https://docs.cloud.google.com/service-mesh/docs/release-notes.md.txt#May_23_2024): Anthos Service Mesh and Traffic Director converged into **Cloud Service Mesh** , introducing the `TRAFFIC_DIRECTOR` control plane implementation for Istio APIs.
- [**July 1, 2024**](https://docs.cloud.google.com/service-mesh/docs/release-notes.md.txt#July_01_2024): New fleets onboarded to managed Cloud Service Mesh began receiving the `TRAFFIC_DIRECTOR` implementation by default.
- **September 8, 2024:** Provisioning of the `ISTIOD` implementation for new fleets ended for general availability (with temporary exceptions for specific organizations in an allowlist).
- [**September 28, 2026**](https://docs.cloud.google.com/service-mesh/docs/release-notes.md.txt#September_28_2026): Formal deprecation announced for both the managed `ISTIOD` control plane implementation and the in-cluster control plane on GKE.