Version 1.12

Prepare to migrate from Istio

Migrating from Istio to Anthos Service Mesh takes some planning. This page provides information to help you prepare for the migration.

Reviewing the supported features

The features Anthos Service Mesh supports differ between platforms. Review the Supported features to see which features are available for your platform. Some features are enabled by default, and others you can optionally enable by creating an IstioOperator configuration file.

Preparing configuration files

If you customized the Istio installation, you need the same customizations when you migrate to Anthos Service Mesh. If you customized the installation by adding the --set values flag, add those settings to an IstioOperator YAML file. When you run the migration script, you pass the YAML file using the --custom_overlay option.

Choosing a certificate authority

You can continue to use Istio CA (previously known as Citadel) as the certificate authority (CA) for issuing mutual TLS (mTLS) certificates, or you can choose to migrate to Anthos Service Mesh certificate authority (Mesh CA).

Unless you require a custom CA, such as HashiCorp Vault, we recommend that you use Mesh CA for the following reasons:

  • Mesh CA is a highly reliable and scalable service that is optimized for dynamically scaled workloads on Google Cloud.
  • With Mesh CA, Google manages the security and availability of the CA backend.
  • Mesh CA lets you rely on a single root of trust across clusters.

What's next?