You are viewing archived v1.21 Service Mesh documentation.
Available versions
Cloud Service Mesh latest
Cloud Service Mesh 1.26 archive
Cloud Service Mesh 1.24 archive
Cloud Service Mesh 1.24 archive
Cloud Service Mesh 1.23 archive
Cloud Service Mesh 1.22 archive
Cloud Service Mesh 1.21 archive
Cloud Service Mesh 1.20 archive
Anthos Service Mesh 1.19 archive
Check control plane implementation
Run the following command to identify your cluster's control plane implementation:
gcloudcontainerfleetmeshdescribe--projectFLEET_PROJECT_IDThe output is similar to the following:
... membershipSpecs: projects/746296320118/locations/us-central1/memberships/demo-cluster-1: mesh: management: MANAGEMENT_AUTOMATIC membershipStates: projects/746296320118/locations/us-central1/memberships/demo-cluster-1: servicemesh: controlPlaneManagement: details: - code: REVISION_READY details: 'Ready: asm-managed' state: ACTIVE implementation: TRAFFIC_DIRECTOR ...The possible values of theimplementation are:
TRAFFIC_DIRECTOR: The core infrastructure of Google Cloud serves as theCloud Service Mesh control plane.ISTIOD: managed instance of istiod serves as the Cloud Service Meshcontrol plane.UPDATING: The cluster is being migrated between implementations. Soon youwill have theTRAFFIC_DIRECTORimplementation.
If you don't seecontrolPlaneManagement.state: ACTIVE this means you don'thave a managed control plane. To confirm that you have an in-cluster controlplane, check for anistiod deployment in youristio-system namespace:
kubectl-nistio-systemgetdeployistiodThe output is similar to the following:
NAME READY UP-TO-DATE AVAILABLE AGEistiod 1/1 1 1 20mExcept as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2026-02-19 UTC.