# Supported features using Istio APIs (managed control plane)

This page describes the supported features and limitations for
Cloud Service Mesh using `TRAFFIC_DIRECTOR` or `ISTIOD` as the control plane and the
differences between each implementation. Note that these are not options you can
choose. The `ISTIOD` implementation is only available for existing users.
New installations use the `TRAFFIC_DIRECTOR` implementation when possible.

For the list of Cloud Service Mesh supported features for an in-cluster
control plane, see
[Using Istio APIs (in-cluster `istiod` control plane)](https://docs.cloud.google.com/service-mesh/v1.25/docs/supported-features-in-cluster.md.txt).
If you're not sure which Cloud Service Mesh control plane you're using, you
can check your control plane implementation using the instructions in
[Identify control plane implementation](https://docs.cloud.google.com/service-mesh/v1.25/docs/check-control-plane-implementation.md.txt)

## Limitations

> [!CAUTION]
> **Caution:** All Cloud Service Mesh clusters for one mesh must be registered to the same fleet at all times to use Cloud Service Mesh. Other clusters in the project of a Cloud Service Mesh cluster must not be registered to a different fleet.

The following limitations apply:

- GKE clusters must be in one of the supported [regions](https://docs.cloud.google.com/service-mesh/v1.25/docs/supported-features-managed.md.txt#regions).
- GKE version must be a supported [version](https://docs.cloud.google.com/service-mesh/v1.25/docs/supported-features-managed.md.txt#environments).
- Only the platforms listed in [Environments](https://docs.cloud.google.com/service-mesh/v1.25/docs/supported-features-managed.md.txt#environments) are supported.
- Pods running with [`hostNetwork: true`](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#podspec-v1-core) are not supported.
- Changing [release channels](https://docs.cloud.google.com/service-mesh/v1.25/docs/managed/select-a-release-channel) is not supported.
- Migrations from [managed Cloud Service Mesh with `asmcli`](https://docs.cloud.google.com/service-mesh/v1.25/docs/managed/provision-managed-anthos-service-mesh-asmcli) to [Cloud Service Mesh with fleet API](https://docs.cloud.google.com/service-mesh/v1.25/docs/managed/provision-managed-anthos-service-mesh) are not supported. Similarly, provisioning managed Cloud Service Mesh with fleet API from `--management manual` to `--management automatic` is not supported.
- Migrations and upgrades are supported only from in-cluster Cloud Service Mesh versions 1.9+ installed with Mesh CA. Installations with Istio CA (previously known as Citadel) must first [migrate to Mesh CA](https://docs.cloud.google.com/service-mesh/v1.25/docs/unified-install/options/ca-migration).
- The limits on scale are outlined in this [guide](https://docs.cloud.google.com/service-mesh/v1.25/docs/operate-and-maintain/scalability-limits.md.txt)
- Only multi-primary deployment option for multi-cluster is supported: primary-remote deployment option for multi-cluster is not.
- `istioctl ps` is not supported. Instead you can use the `gcloud beta container fleet mesh debug` commands as described in [Troubleshooting](https://docs.cloud.google.com/service-mesh/v1.25/docs/troubleshooting/troubleshoot-intro.md.txt).
- Unsupported APIs:

  - `EnvoyFilter` API

  - `WasmPlugin` API

  - `IstioOperator` API

  - `Kubernetes Ingress` API

  > [!NOTE]
  > **Note:** You can still enable optional features without using the IstioOperator API, see [Enable optional features on managed Cloud Service Mesh](https://docs.cloud.google.com/service-mesh/v1.25/docs/enable-optional-features-managed.md.txt). You can also use the migration tool included with `asmcli` to automatically convert other `IstioOperator` optional features to be compatible with managed control plane. For more information, see [Migrate from `IstioOperator`](https://docs.cloud.google.com/service-mesh/v1.25/docs/migrate-istio-operator).

- For a list of unsupported API fields, see [Unsupported Istio APIs in Managed Cloud Service Mesh](https://docs.cloud.google.com/service-mesh/v1.25/docs/onboarding/unsupported-istio-apis.md.txt).

- You can use the managed control plane without a GKE Enterprise subscription,
  but certain UI elements and features in Google Cloud console are only available
  to GKE Enterprise subscribers. For information about what is available
  to subscribers and non-subscribers, see
  [GKE Enterprise and Cloud Service Mesh UI differences](https://docs.cloud.google.com/service-mesh/v1.25/docs/ui-differences.md.txt).

- 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
  be overwritten.

- Managed Cloud Service Mesh only supports the default DNS domain `.cluster.local`.

- New installations of managed Cloud Service Mesh fetch JWKS only using
  Envoys, unless the fleet contains other clusters for which that behavior is
  not enabled. This is equivalent to the `PILOT_JWT_ENABLE_REMOTE_JWKS=envoy`
  Istio option. Compared to installations that don't have VPCSC_GA_SUPPORTED
  condition (see below), you might need extra configuration for `ServiceEntry`
  and `DestinationRule` configurations. For an example, see
  [`requestauthn-with-se.yaml.tmpl`](https://github.com/istio/istio/blob/master/tests/integration/security/remote_jwks/testdata/requestauthn-with-se.yaml.tmpl).
  You can determine whether the current mode of operation is equivalent to
  `PILOT_JWT_ENABLE_REMOTE_JWKS=envoy` by determining whether [VPC Service
  Controls](https://docs.cloud.google.com/service-mesh/v1.25/docs/managed/vpc-sc) are supported for the control
  plane (ie. the VPCSC_GA_SUPPORTED condition is displayed).

- Managed data plane is only supported for workloads without additional sidecars
  (other than the Cloud Service Mesh sidecar).

## Control plane differences

There are differences in supported features between the `ISTIOD` and `TRAFFIC_DIRECTOR`
control plane implementations. To check which implementation you are using, see
[Identify control plane implementation](https://docs.cloud.google.com/service-mesh/v1.25/docs/check-control-plane-implementation.md.txt).

- Yes -- indicates the feature is available and enabled by default.
- Yes† - indicates that feature APIs may have differences between various platforms.
- Yes\* -- indicates the feature is supported for the platform and can be enabled, as described in [Enable optional features](https://docs.cloud.google.com/service-mesh/v1.25/docs/enable-optional-features) or the feature guide linked in the feature table.
- No§ -- indicates that the feature is supported by allowlist. Previous users of managed Anthos Service Mesh are automatically allowlisted at the [organization](https://docs.cloud.google.com/resource-manager/docs/cloud-platform-resource-hierarchy.md.txt#organizations) level. [Contact Google Cloud Support](https://docs.cloud.google.com/service-mesh/v1.25/docs/getting-support.md.txt) to request access or to check your allowlist status.
- No -- indicates either the feature isn't available or it isn't supported.

The default and optional features are fully supported by Google Cloud
Support. Features not explicitly listed in the tables receive best-effort
support.

### What determines control plane implementation

When you provision managed Cloud Service Mesh the first time in a fleet, we
determine which control plane implementation to use. The same implementation is
used for all clusters that provision managed Cloud Service Mesh in that fleet.

New fleets that onboard to managed Cloud Service Mesh receive the
`TRAFFIC_DIRECTOR` control plane implementation, with certain exceptions:

- If you are an existing managed Cloud Service Mesh user, you receive the `ISTIOD` control plane implementation when you onboard a new fleet in the same Google Cloud Organization to managed Cloud Service Mesh, until at least June 30, 2024. If you are one of these users, you can contact Support to fine-tune this behavior. Users whose existing usage is not compatible with the `TRAFFIC_DIRECTOR` implementation without changes will continue to receive the `ISTIOD` implementation until September 8, 2024. (These users received a Service Announcement.)
- If any GKE on Google Cloud cluster in your fleet contains an in-cluster Cloud Service Mesh control plane when you provision managed Cloud Service Mesh, you will receive the `ISTIOD` control plane implementation.
- If any cluster in your fleet uses [GKE Sandbox](https://docs.cloud.google.com/kubernetes-engine/docs/concepts/sandbox-pods.md.txt), when you provision managed Cloud Service Mesh, you receive the `ISTIOD` control plane implementation.

## Managed control plane supported features

### Install, upgrade, and rollback

| Feature | Managed (TD) | Managed (istiod) |
|---|---|---|
| Installation on GKE clusters using [fleet](https://docs.cloud.google.com/anthos/multicluster-management/fleets) feature API | Yes | Yes |
| Upgrades from ASM 1.9 versions that use Mesh CA | Yes | Yes |
| Direct (skip-level) upgrades from Cloud Service Mesh versions prior to 1.9 (see notes for indirect upgrades) | No | No |
| Direct (skip-level) upgrades from Istio OSS (see notes for indirect upgrades) | No | No |
| Direct (skip-level) upgrades from Istio-on-GKE add-on (see notes for indirect upgrades) | No | No |
| Enabling [optional features](https://docs.cloud.google.com/service-mesh/v1.25/docs/managed-service-mesh-optional-features) | Yes | Yes |

> [!NOTE]
> **Note:** Indirect migrations and upgrades are supported, meaning that you can follow the standard Cloud Service Mesh [upgrade paths](https://docs.cloud.google.com/service-mesh/v1.25/docs/upgrade-path-old-versions-gke) through each version until you reach Cloud Service Mesh 1.25 with an in-cluster control plane, then you can migrate to the managed control plane. Direct migrations and upgrades are supported only from Cloud Service Mesh versions 1.9 or later installed with Mesh CA. Installations with Istio CA must first migrate to Mesh CA.

### Environments

| Feature | Managed (TD) | Managed (istiod) |
|---|---|---|
| GKE versions [currently available in release channels](https://docs.cloud.google.com/kubernetes-engine/docs/release-notes.md.txt#current_versions), in one of the supported [regions](https://docs.cloud.google.com/service-mesh/v1.25/docs/supported-features-managed.md.txt#regions) | Yes | Yes |
| GKE versions [currently available in release channels](https://docs.cloud.google.com/kubernetes-engine/docs/release-notes.md.txt#current_versions), in one of the supported [regions](https://docs.cloud.google.com/service-mesh/v1.25/docs/supported-features-managed.md.txt#regions), GKE [Autopilot](https://docs.cloud.google.com/kubernetes-engine/docs/concepts/autopilot-overview.md.txt) clusters | Yes | Yes |
| Environments outside of Google Cloud (GKE Enterprise on-premises, GKE Enterprise on other public clouds, Amazon EKS, Microsoft AKS, or other Kubernetes clusters) | No | No |

### Scale

| Feature | Managed (TD) | Managed (istiod) |
|---|---|---|
| 1000 services and 5000 workloads per cluster | Yes | Yes |
| 50 [Headless Service Ports](https://kubernetes.io/docs/concepts/services-networking/service/#headless-services) per mesh and 36 pods per Headless ServicePort | Yes | Yes |

> [!NOTE]
> **Note:** This is a soft limit on the number of services and workloads supported per cluster. Reach out to Cloud Support when exceeding this limit.

### Platform environment

| Feature | Managed (TD) | Managed (istiod) |
|---|---|---|
| Single network | Yes | Yes |
| Multi-network | No | No |
| Single-project | Yes | Yes |
| Multi-project with Shared VPC | Yes | Yes |

### Multi-cluster deployment

| Feature | Managed (TD) | Managed (istiod) |
|---|---|---|
| Multi-primary | Yes | Yes |
| Primary-remote | No | No |
| Multi-cluster endpoint discovery with [declarative API](https://docs.cloud.google.com/service-mesh/v1.25/docs/unified-install/gke-install-multi-cluster#endpoint-discovery-declarative-api) | Yes | Yes |
| Multi-cluster endpoint discovery with [remote secrets](https://docs.cloud.google.com/service-mesh/v1.25/docs/unified-install/gke-install-multi-cluster#configure_endpoint_discovery_between_public_clusters) | No | Yes |
| Multi-cluster endpoint discovery with [declarative API](https://docs.cloud.google.com/service-mesh/v1.25/docs/unified-install/gke-install-multi-cluster#endpoint-discovery-declarative-api) and a simple topology | Yes | Yes |

**Notes on terminology**

- A multi-primary configuration means that the configuration must be replicated in all clusters.
- A primary-remote configuration means that a single cluster contains the configuration and is considered the source of truth.
- Cloud Service Mesh uses a simplified definition of network based on general connectivity. Workload instances are on the same network if they are able to communicate directly, without a gateway.
- Simple topology for multi-cluster endpoint discovery means that every cluster in the fleet either participates or does not participate in endpoints discovery. Complex topologies that are unsupported include (a) one-way endpoint discover (e.g. cluster A can discover endpoints in cluster B but not vice versa) and (b) disjointed endpoint discovery networks (e.g. clusters A and B can discover each other's endpoints, clusters C and D can discover each other's endpoints, but A/B and C/D cannot discover each other's endpoints).

### Base Images

| Feature | Managed (TD) | Managed (istiod) |
|---|---|---|
| [Distroless proxy image](https://docs.cloud.google.com/service-mesh/v1.25/docs/enable-optional-features-managed.md.txt#distroless_proxy_image) | Yes | Yes |

† Cloud Service Mesh with a managed (TD) control plane only supports
the distroless image type. You cannot change it.

Note that distroless images have minimal binaries, so you cannot exec the usual
commands like bash or curl because they are not present in the distroless image.
However, you can use ephemeral containers to attach to a running workload Pod to
be able to inspect it and run custom commands. For example, see
[Collecting Cloud Service Mesh logs](https://docs.cloud.google.com/service-mesh/v1.25/docs/troubleshooting/troubleshoot-collect-logs.md.txt#configure_envoy_proxy).

## Security

#### VPC Service Controls

| Feature | Managed (TD) | Managed (istiod) |
|---|---|---|
| [VPC Service Controls](https://docs.cloud.google.com/service-mesh/v1.25/docs/managed/vpc-sc.md.txt) | Yes | Yes |

### Certificate distribution and rotation mechanisms

| Feature | Managed (TD) | Managed (istiod) |
|---|---|---|
| Workload certificate management | Yes | Yes |
| External certificate management on [ingress](https://istio.io/v1.24/docs/tasks/traffic-management/ingress/secure-ingress/) and [egress](https://istio.io/latest/docs/tasks/traffic-management/egress/egress-gateway-tls-origination/) gateways. | Yes | Yes |

### Certificate authority (CA) support

| Feature | Managed (TD) | Managed (istiod) |
|---|---|---|
| Cloud Service Mesh certificate authority | Yes | Yes |
| [Certificate Authority Service](https://docs.cloud.google.com/service-mesh/v1.25/docs/security/certificate-authority-service.md.txt) | Yes | Yes |
| Istio CA | No | No |
| Integration with custom CAs | No | No |

### Security features

In addition to supporting Istio security features, Cloud Service Mesh
provides even more capabilities to help you secure your applications.

| Feature | Managed (TD) | Managed (istiod) |
|---|---|---|
| [IAP integration](https://docs.cloud.google.com/service-mesh/v1.25/docs/security/iap-integration.md.txt) | Yes | Yes |
| [End-user authentication](https://docs.cloud.google.com/service-mesh/v1.25/docs/unified-install/options/end-user-auth) | Yes | Yes |
| [Dry-run mode](https://docs.cloud.google.com/service-mesh/v1.25/docs/security/authorization-advanced-features.md.txt#dry-run_mode) | Yes | Yes |
| [Denial logging](https://docs.cloud.google.com/service-mesh/v1.25/docs/security/authorization-advanced-features.md.txt#denial_logging) | Yes | Yes |
| Audit policies (not supported) | No | No |

### Authorization policy

| Feature | Managed (TD) | Managed (istiod) |
|---|---|---|
| Authorization v1beta1 policy | Yes† | Yes |
| CUSTOM Authorization Policy | No§ | Yes |

† The `TRAFFIC_DIRECTOR` control plane implementation does not support the
`rules.from.source.RemoteIp` and `rules.from.source.NotRemoteIp` fields.

### Peer authentication

| Feature | Managed (TD) | Managed (istiod) |
|---|---|---|
| Auto-mTLS | Yes | Yes |
| mTLS PERMISSIVE mode | Yes | Yes |
| mTLS STRICT mode | Yes \* | Yes \* |
| mTLS DISABLE mode | No | Yes |

#### Request authentication

| Feature | Managed (TD) | Managed (istiod) |
|---|---|---|
| JWT authentication^[(Note 1)](https://docs.cloud.google.com/service-mesh/v1.25/docs/supported-features-managed.md.txt#sectionjwt)^ | Yes | Yes |
| JWT Claim Based Routing^[](https://istio.io/latest/docs/tasks/security/authentication/jwt-route/)^ | No | Yes |
| JWT Copy Claim to Headers^[](https://istio.io/latest/docs/tasks/security/authentication/claim-to-header/)^ | No | Yes |

**Notes:**

1. Third-party JWT is enabled by default.
2. Add the full fqdn/hostname in JWKSURI while defining RequestAuthentication API.
3. Managed control plane enforces Envoy to fetch JWKS when specifying JWKS URI.

## Telemetry

### Metrics

| Feature | Managed (TD) | Managed (istiod) |
|---|---|---|
| Cloud Monitoring (HTTP in-proxy metrics) | Yes | Yes |
| Cloud Monitoring (TCP in-proxy metrics) | No | No |
| Prometheus metrics export to Grafana (Envoy metrics only) | Yes \* | Yes \* |
| Prometheus metrics export to Kiali | No | No |
| Google Cloud Managed Service for Prometheus, not including the Cloud Service Mesh dashboard | Yes \* | Yes \* |
| [Istio Telemetry API](https://preliminary.istio.io/latest/docs/tasks/observability/telemetry/) | No † | No |
| Custom adapters/backends, in or out of process | No | No |
| Arbitrary telemetry and logging backends | No | No |

† The `TRAFFIC_DIRECTOR` control plane supports a subset of Istio telemetry API
used to configure [access logs](https://docs.cloud.google.com/service-mesh/v1.25/docs/observability/access-logs.md.txt) and
[trace](https://docs.cloud.google.com/service-mesh/v1.25/docs/observability/accessing-traces.md.txt). The `TRAFFIC_DIRECTOR`
control plane does not support configuring the trace sampling rate.

> [!NOTE]
> **Note:** You can configure third-party telemetry products (such as Grafana, and Prometheus), but we cannot guarantee future compatibility and Cloud Support cannot provide help managing them.

### Proxy request logging

| Feature | Managed (TD) | Managed (istiod) |
|---|---|---|
| [Traffic logs](https://docs.cloud.google.com/service-mesh/v1.25/docs/observability/accessing-logs#traffic_logs) | Yes | Yes |
| [Access logs](https://docs.cloud.google.com/service-mesh/v1.25/docs/observability/accessing-logs#access_logs) | Yes \* | Yes \* |

### Tracing

| Feature | Managed (TD) | Managed (istiod) |
|---|---|---|
| Cloud Trace | Yes \* | Yes \* |
| Jaeger tracing (allows use of customer-managed Jaeger) | No | Compatible |
| Zipkin tracing (allows use of customer-managed Zipkin) | No | Compatible |

> [!NOTE]
> **Note:** You can configure third-party telemetry products (such as Jaeger, Zipkin, and Grafana), but we cannot guarantee future compatibility and Cloud Support cannot provide help managing them.

## Networking

### Traffic interception and redirection mechanisms

| Feature | Managed (TD) | Managed (istiod) |
|---|---|---|
| Use of `iptables` using `init` containers with `CAP_NET_ADMIN` | No | Yes |
| Istio Container Network Interface (CNI) | Yes | Yes |
| Whitebox sidecar | No | No |

† We strongly recommend using Container Network Interface (CNI) instead of
`init` containers.

### Protocol support

| Feature | Managed (TD) | Managed (istiod) |
|---|---|---|
| IPv4 | Yes | Yes |
| HTTP/1.1 | Yes | Yes |
| HTTP/2 | Yes | Yes |
| TCP byte streams [(Note 1)](https://docs.cloud.google.com/service-mesh/v1.25/docs/supported-features-managed.md.txt#section1) | Yes | Yes |
| [gRPC](https://grpc.io) | Yes | Yes |
| IPv6 | Yes | No |

**Notes:**

1. Although TCP is a supported protocol for networking and TCP metrics are collected, they are not reported. Metrics are displayed only for HTTP services in the Google Cloud console.
2. Services that are configured with Layer 7 capabilities for the following protocols are not supported: WebSocket, MongoDB, Redis, MySQL, 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 Cloud Service Mesh's routing logic), then the protocol isn't supported. Although gateway ports can be created with Mongo, MySQL and Redis protocol, the mesh treats the resulting traffic as standard TCP, lacking protocol-specific handling.
3. † In proxyless gRPC, IPv6 dual-stack features are supported only in gRPC 1.66.1 or newer in [C++](https://github.com/grpc/grpc/releases/tag/v1.66.1) and [Python](https://pypi.org/project/grpcio/1.66.1), [gRPC Go v1.71](https://github.com/grpc/grpc-go/releases/tag/v1.71.0), and or [gRPC Node.js v1.12](https://github.com/grpc/grpc-node/releases/tag/%40grpc%2Fgrpc-js-xds%401.12.0). If you try to configure dual-stack features with a version of gRPC that doesn't support dual-stack, the clients will use only the first address sent by Traffic Director.

### Envoy deployments

| Feature | Managed (TD) | Managed (istiod) |
|---|---|---|
| Sidecars | Yes | Yes |
| Ingress gateway | Yes | Yes |
| Egress directly out from sidecars | Yes | Yes |
| Egress using egress gateways | Yes \* | Yes \* |

### CRD support

| Feature | Managed (TD) | Managed (istiod) |
|---|---|---|
| Sidecar resource | Yes | Yes |
| Service entry resource | Yes | Yes |
| Percentage, fault injection, path matching, redirects, retries, rewriting, timeout, retry, mirroring, header manipulation, and CORS routing rules | Yes | Yes |
| [\`EnvoyFilter\` API](https://istio.io/docs/reference/config/networking/v1alpha3/envoy-filter/) | No§ | No |
| [\`WasmPlugin\` API](https://istio.io/latest/docs/reference/config/proxy_extensions/wasm-plugin/) | No | No |
| Istio Operator | No | No |

### Load balancer for the Istio ingress gateway

| Feature | Managed (TD) | Managed (istiod) |
|---|---|---|
| Third-party external load balancer | Yes | Yes |
| Google Cloud Internal load balancer | Yes \* | Yes \* |

### Service mesh cloud gateway

| Feature | Managed (TD) | Managed (istiod) |
|---|---|---|
| Service mesh cloud gateway | Yes | Yes |

### Kubernetes Gateway API

| Feature | Managed (TD) | Managed (istiod) |
|---|---|---|
| Kubernetes Gateway API | No | No |

### Load balancing policies

| Feature | Managed (TD) | Managed (istiod) |
|---|---|---|
| Round robin | Yes | Yes |
| Least connections | Yes | Yes |
| Random | Yes | Yes |
| Passthrough | Yes | Yes |
| Consistent hash | Yes | Yes |
| Locality | Yes | Yes |
| GCPTrafficDistributionPolicy | Yes | No |
| GCPBackendPolicy | Yes | No |

### Service entry

| Feature | Managed (TD) | Managed (istiod) |
|---|---|---|
| ServiceEntry v1beta1 | Yes† | Yes |

† The `TRAFFIC_DIRECTOR` control plane implementation does not support following
fields and values in fields:

- `workloadSelector` field
- `endpoints[].network` field
- `endpoints[].locality` field
- `endpoints[].weight` field
- `endpoints[].serviceAccount` field
- `DNS_ROUND_ROBIN` value in `resolution` field
- `MESH_INTERNAL` value in `location` field
- Unix domain socket address in `endpoints[].address` field
- `subjectAltNames` field
- Two or more `endpoints[]` entries if `resolution` field has `DNS` value

### Destination rule

| Feature | Managed (TD) | Managed (istiod) |
|---|---|---|
| DestinationRule v1beta1 | Yes† | Yes |

† The `TRAFFIC_DIRECTOR` control plane implementation does not support following fields.

- `trafficPolicy.loadBalancer.localityLbSetting` field
- `trafficPolicy.tunnel` field
- `trafficPolicy.tls.credentialName` field
- `trafficPolicy.portLevelSettings[].tls.credentialName` field

Additionally, the `TRAFFIC_DIRECTOR` control plane implementation requires that the
destination rule defining subsets is in the same namespace and cluster with
the Kubernetes service or ServiceEntry.

### Sidecar

| Feature | Managed (TD) | Managed (istiod) |
|---|---|---|
| Sidecar v1beta1 | Yes† | Yes |

† The `TRAFFIC_DIRECTOR` control plane implementation does not support following
fields and values in fields:

- `ingress` field
- `egress.port` field
- `egress.bind` field
- `egress.captureMode` field
- `inboundConnectionPool` field

### DNS proxy

| Feature | Managed (TD) | Managed (istiod) |
|---|---|---|
| Name resolution of `Service` across clusters | Yes† | Yes |
| Name resolution of `ServiceEntry` in a cluster | Yes† | Yes |
| Name resolution of [Headless `Service`](https://kubernetes.io/docs/concepts/services-networking/service/#headless-services) | No | Yes |
| [Address auto allocation](https://istio.io/latest/docs/ops/configuration/traffic-management/dns-proxy/#address-auto-allocation) | No | Yes |

† `1.21.5-asm.39` or later version of the sidecar is required.

## MeshConfig

| Feature | Managed (TD) | Managed (istiod) |
|---|---|---|
| DiscoverySelectors | Yes | Yes |
| clusterLocal | Yes | Yes |
| LocalityLB | No§ | Yes |
| ExtensionProviders | No§ | Yes |
| CACert | No | Yes |
| ImageType - distroless | No§ | Yes |
| OutboundTrafficPolicy | No§ | Yes |
| defaultProviders.accessLogging | No | No |
| defaultProviders.tracing | No | No |
| defaultConfig.tracing.stackdriver | No§ | Yes |
| accessLogFile | No§ | Yes |

## ProxyConfig

| Feature | Managed (TD) | Managed (istiod) |
|---|---|---|
| HTTP/1.0 support (ISTIO_META_NETWORK) | No | Yes |
| Image selection (distroless or base image) | No† | Yes |
| [Kubernetes native sidecar](https://kubernetes.io/blog/2023/08/25/native-sidecar-containers) (ENABLE_NATIVE_SIDECARS) | No | No |

† [Distroless image](https://docs.cloud.google.com/service-mesh/v1.25/docs/enable-optional-features-managed.md.txt#distroless_proxy_image) is used for the injection.

## Regions

GKE clusters must be in one of the following regions or any zone
within the following regions.

| Region | Location |
|---|---|
| `africa-south1` | Johannesburg |
| `asia-east1` | Taiwan |
| `asia-east2` | Hong Kong |
| `asia-northeast1` | Tokyo, Japan |
| `asia-northeast2` | Osaka, Japan |
| `asia-northeast3` | South Korea |
| `asia-south1` | Mumbai, India |
| `asia-south2` | Delhi, India |
| `asia-southeast1` | Singapore |
| `asia-southeast2 ` | Jakarta |
| `australia-southeast1` | Sydney, Australia |
| `australia-southeast2` | Melbourne, Australia |
| `europe-central2` | Poland |
| `europe-north1` | Finland |
| `europe-southwest1` | Spain |
| `europe-west1` | Belgium |
| `europe-west2` | England |
| `europe-west3` | Frankfurt, Germany |
| `europe-west4` | Netherlands |
| `europe-west6` | Switzerland |
| `europe-west8` | Milan, Italy |
| `europe-west9` | France |
| `europe-west10` | Berlin, Germany |
| `europe-west12` | Turin, Italy |
| `me-central1` | Doha |
| `me-central2` | Dammam, Saudi Arabia |
| `me-west1` | Tel Aviv |
| `northamerica-northeast1` | Montreal, Canada |
| `northamerica-northeast2` | Toronto, Canada |
| `southamerica-east1` | Brazil |
| `southamerica-west1` | Chile |
| `us-central1` | Iowa |
| `us-east1` | South Carolina |
| `us-east4` | Northern Virginia |
| `us-east5` | Ohio |
| `us-south1` | Dallas |
| `us-west1` | Oregon |
| `us-west2` | Los Angeles |
| `us-west3` | Salt Lake City |
| `us-west4` | Las Vegas |

## User interface

| Feature | Managed (TD) | Managed (istiod) |
|---|---|---|
| Cloud Service Mesh dashboards in the Google Cloud console | Yes | Yes |
| Cloud Monitoring | Yes | Yes |
| Cloud Logging | Yes | Yes |

## Tooling

| Feature | Managed (TD) | Managed (istiod) |
|---|---|---|
| `gcloud beta container fleet mesh debug ` tool | Yes | Yes |