Stay organized with collections
Save and categorize content based on your preferences.
This page describes the supported features and limitations for managed
Anthos Service Mesh. For the list of Anthos Service Mesh supported features for
Anthos Service Mesh with an in-cluster control plane, see
In-cluster control plane.
The following limitations apply:
GKE clusters must be in one of the supported regions.
Migrations and upgrades are supported only from in-cluster Anthos Service Mesh
versions 1.9+ installed with Mesh CA. Installations with Istio CA (previously
known as Citadel) must first
migrate to Mesh CA.
Scale is limited to 1000 services and 5000 workloads per cluster.
Only multi-primary deployment option for multi-cluster is supported:
primary-remote deployment option for multi-cluster is not.
istioctl ps is not supported, however you can use istioctl pc with the pod name and namespace instead.
Unsupported Istio APIs:
You can use the managed control plane without an Anthos subscription,
but certain UI elements and features in Google Cloud console are only available
to Anthos subscribers. For information about what is available
to subscribers and non-subscribers, see
Anthos and Anthos Service Mesh UI differences.
During the provisioning process for a managed control plane,
Istio CRDs corresponding to the selected channel are installed in the
specified cluster. If there are existing Istio CRDs in the cluster, they will
GKE private clusters with public endpoint access, with or without Master
Authorized Network (MAN) enabled. In private clusters, the
GKE control plane (master) has a
private and public endpoint. There are three configuration
combinations to control access to the cluster endpoints:
Although TCP is a supported protocol for networking, TCP
metrics aren't collected or reported. Metrics are displayed only for HTTP
services in the Google Cloud console.
Services that are configured with Layer 7 capabilities for
the following protocols are not supported: WebSocket, MongoDB, Redis, Kafka,
Cassandra, RabbitMQ, Cloud SQL. You might be able to make the protocol work by
using TCP byte stream support. If TCP byte stream cannot support the protocol
(for example, Kafka sends a redirect address in a protocol-specific reply and
this redirect is incompatible with Anthos Service Mesh's routing logic), then the
protocol isn't supported.
Egress directly out from sidecars
Egress using egress gateways
Service entry resource
Percentage, fault injection, path matching, redirects, retries, rewriting,
timeout, retry, mirroring, header manipulation, and CORS routing rules