The guidance for using proxy image types (default and distroless) with
Share
Services
## Feature
Feature
The guidance for using proxy image types (`default` and `distroless`) with Managed Cloud Service Mesh has been updated:
* **Directly onboarded clusters** using the `TRAFFIC_DIRECTOR` implementation use `distroless` proxy images by default, and other image types are not supported.
* **Migrated clusters** (migrated from `ISTIOD` to `TRAFFIC_DIRECTOR`) default to `default` images, but can opt in to `distroless` images via `MeshConfig` or the `sidecar.istio.io/proxyImageType: distroless` Pod annotation.
For more information, see[Distroless proxy images](https://docs.cloud.google.com/service-mesh/docs/enable-optional-features-managed#distroless%5Fproxy%5Fimage)and[Identify the proxy image type used in the cluster](https://docs.cloud.google.com/service-mesh/docs/troubleshooting/troubleshoot-proxy#identify%5Fproxy%5Fimage%5Ftype).
What else is happening at Google Cloud Platform?
Read update
Services
Share
Read update
Services
Share
You can now monitor the performance, adoption, latency, and costs of your data agents and their
about 22 hours ago
Services
Share