[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-08-26。"],[],[],null,["# Supported platforms\n\nCloud Service Mesh supports a variety of infrastructures (GKE/Kubernetes,\nCompute Engine) and environments (on-premises, other clouds). This page\ndescribes the APIs and options for using Cloud Service Mesh across all of\nthese options.\n\nOn Google Cloud\n---------------\n\nThere are two choices of APIs on Google Cloud based on which infrastructure you\nplan to use.\n\nIf your workloads are exclusively on GKE, use the Istio APIs.\n\n- Use the fleet API to install Cloud Service Mesh on clusters in the fleet.\n\n- Choose the CA you want to use, MeshCA or CAS. The clusters in the fleet will\n all use the same CA, establishing trust across the workloads running on the\n clusters.\n\n- The Service Mesh UI is enabled automatically.\n\n### Managed control plane for GKE\n\nThe control plane provisioned for these clusters depends on whether you are\nadding clusters to an existing fleet or are provisioning a new fleet.\n\nNew fleets use the global, managed control plane. This control plane scales\nacross the entire Google Cloud network and provides enhanced reliability and\nstability.\n\nIf you are adding clusters to an existing fleet, new clusters will use the\nsame managed control plane implementation as existing clusters.\n\n### Unmanaged Cloud Service Mesh\n\nThere is also an option to use an unmanaged, in-cluster control plane. Google\nstrongly recommends using managed Cloud Service Mesh to let Google update and\nmaintain the mesh infrastructure. This option should only be used if the managed\nCloud Service Mesh does not support your use case. It requires users to\nperform regular releases and patches to keep the system updated.\n\n### VMs, GKE and or Proxyless gRPC\n\nIf your workloads are a combination of VMs and GKE, or use\nproxyless gRPC, you should use the\n[Service Routing APIs](/service-mesh/docs/service-routing/service-routing-overview).\nThese APIs let you define a mesh and configure the routing between services in\nthat mesh.\n\nOff Google Cloud\n----------------\n\nCloud Service Mesh supports GKE and attached clusters in a\nvariety of environments. In this case, Cloud Service Mesh is part of\nGKE Enterprise on Google Cloud. Cloud Service Mesh is supported the following\nenvironments:\n\n- Google Distributed Cloud (software only) for VMware\n- Google Distributed Cloud (software only) for bare metal\n- GKE on AWS\n- GKE on Azure\n- EKS Kubernetes clusters on AWS\n- AKS Kubernetes clusters on Azure\n\nIn these environments Cloud Service Mesh is installed in-cluster using\n`asmcli`. The Istio APIs are installed in the cluster enabling the user to\nconfigure the service mesh for Kubernetes workloads.\n\n1.26.x\n------\n\nOnly the following environments are supported for in-cluster Cloud Service Mesh\n1.26.x. All other environments are unsupported.\n\n1.25.x\n------\n\nOnly the following environments are supported for in-cluster Cloud Service Mesh\n1.25.x. All other environments are unsupported.\n\n1.24.x\n------\n\nOnly the following environments are supported for in-cluster Cloud Service Mesh\n1.24.x. All other environments are unsupported.\n\nFor a list of environments that are supported for managed Cloud Service Mesh,\nsee\n[managed Cloud Service Mesh Environments](/service-mesh/docs/managed/supported-features-mcp#environments)."]]
