[[["易于理解","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-19。"],[],[],null,["# About the asmcli\n================\n\nThe `asmcli` is a Google-provided tool that you can use to install or\nupgrade Cloud Service Mesh. If you let it, `asmcli` will configure your\nproject and cluster as follows:\n\n- Grant you the required Identity and Access Management (IAM) permissions on your Google Cloud project.\n- Enable the required Google APIs on your Google Cloud project.\n- Set a label on the cluster that identifies the mesh.\n- Create a service account that lets data plane components, such as the sidecar proxy, securely access your project's data and resources.\n- [Register the cluster](/anthos/multicluster-management/connect/registering-a-cluster) to the fleet if it isn't already registered.\n\nJust include the `--enable_all` flag when you run `asmcli` to let it configure\nyour project and cluster. For more information about `asmcli` options and flags,\nsee the [`asmcli` reference](/service-mesh/v1.19/docs/unified-install/reference).\n\nNext, `asmcli` configures YAML files with your project and cluster information.\nThese configuration files are needed to install the Cloud Service Mesh control plane.\n\nIf you are new to Cloud Service Mesh and Istio, skip ahead to\n[Supported platforms](#supported_platforms). The next section is intended to\nhelp existing Cloud Service Mesh upgrade to 1.19.\n\nTransitioning to `asmcli`\n-------------------------\n\nThe `asmcli` takes the place of `istioctl install` and `install_asm`. Although\nyou can still use the legacy tools in Cloud Service Mesh 1.11, we are deprecating\nthem and they will no longer be supported in Cloud Service Mesh 1.12 and later.\nPlease update your scripts and tools to use `asmcli`.\n\nWith Cloud Service Mesh 1.11 and later, all clusters must be registered to a\n[fleet](/anthos/multicluster-management/fleets). See\n[Fleet requirements](/service-mesh/v1.19/docs/unified-install/anthos-service-mesh-prerequisites#fleet_requirements)\nfor details.\n\n### Transitioning from `install_asm`\n\nIf you are familiar with `install_asm`, `asmcli` is similar but with the\nfollowing notable differences:\n\n- You use `asmcli install` for new installations and upgrades.\n There isn't a\n [`--mode` option](/service-mesh/v1.19/docs/unified-install/reference#options) like with\n `install_asm`. When you run `asmcli install`, it checks to see if\n there's an existing control plane on the cluster. If there isn't an existing\n control plane, `asmcli` installs Cloud Service Mesh. If the cluster has an\n existing control plane (either a Cloud Service Mesh control plane or an open source\n Istio control plane):\n\n - If the revision label on the existing control plane doesn't match the\n revision label for the new control plane, `asmcli` does a\n [canary upgrade](/service-mesh/v1.19/docs/unified-install/plan-upgrade#about_canary_upgrades).\n\n - If the control plane revision labels are the same, `asmcli` does an in-place\n upgrade.\n\n- Most of the `asmcli`\n [options and flags](/service-mesh/v1.19/docs/unified-install/reference) behave the same\n as the ones for `install_asm`.\n\n### Transitioning from `istioctl install`\n\nIf you are familiar with `istioctl install`, if you normally pass an\n`IstioOperator` YAML file using the `-f` command-line argument to configure the\ncontrol plane, you can pass the file to `asmcli` using the `--custom_overlay`\noption. In the Cloud Service Mesh documentation, we refer to these files as overlay\nfiles.\n| **Note:** By default, `asmcli` doesn't install an ingress gateway with the control plane. For production deployments, we recommend that you install gateways separately. For more information and best practices, see [Install and upgrade gateways](/service-mesh/v1.19/docs/gateways#best_practices_for_deploying_gateways). We have provided sample Deployment, Service, ServiceAccount, and Role configuration files in the [`anthos-service-mesh`](https://github.com/GoogleCloudPlatform/anthos-service-mesh-packages/tree/main/samples/gateways) repository for both ingress and egress gateways to get you started. You can deploy them as they are or customize them as needed.\n\nSupported platforms\n-------------------\n\nCloud Service Mesh installations on the list of\n[Supported platforms](/service-mesh/v1.19/docs/supported-platforms) can be configured\nor upgraded by `asmcli`.\n\nHowever, not all features are available on the platforms outside of Google Cloud.\nFor details, see\n[In-cluster control plane supported features](/service-mesh/v1.19/docs/supported-features).\n\nWhat's next\n-----------\n\n- [Prerequisites](/service-mesh/v1.19/docs/unified-install/anthos-service-mesh-prerequisites)"]]