You can see the latest product updates for all of Google Cloud on the Google Cloud release notes page.
To get the latest product updates delivered to you, add the URL of this page to your
reader, or add the feed URL directly:
March 27, 2020
Istio 1.4.6-gke.0 - This is the initial release of Istio 1.4 to Istio on GKE
March 13, 2020
Istio 1.2.10-gke.3 - Fixes known security issues with the same fixes as OSS Istio 1.4.6:
- CVE-2020-8659, CVE-2020-8661, CVE-2020-8664, CVE-2020-8660: ISTIO-SECURITY-2020-003
February 19, 2020
Istio 1.2.10-gke.1 - Fixes the following known security issues:
December 13, 2019
Istio 1.2.7-gke.0 - This release has a known security issue that can leave clusters vulnerable. We recommend upgrading to a version of GKE that will install Istio 1.2.10.
Istio 1.1.16-gke.0 - This release has a known security issue that can leave clusters vulnerable. We recommend upgrading to a version of GKE that will install Istio 1.1.17.
Istio 1.1.17-gke.0 - Fixes a known security issue.
November 12, 2019
For the following versions:
- Istio 1.0.3-gke.0
- Istio 1.0.3-gke.3a
- Istio 1.0.3-gke.3b
- Istio 1.0.6-gke.1
- Istio 1.0.6-gke.3
- Istio 1.0.9-gke.0
- Istio 1.1.7-gke.0
- Istio 1.1.10-gke.0
- Istio 1.1.13-gke.0
- Istio 1.1.16-gke.0
- Istio 1.1.3-gke.0
Depending on when the cluster was first created, may have a root certificate that will expire soon. Please follow the instructions to check the expiration date and, optionally, extend the life of your root certificate.
October 10, 2019
August 13, 2019
Istio 1.1.13-gke-0 - Fixes a known security issue with the same fixes as OSS Istio version 1.1.13.
July 11, 2019
June 27, 2019
Istio 1.1.7-gke.0 - Google Cloud's operations suite tracing is disabled by default.
Istio 1.1.7-gke.0 - Fixes a known security issue from version 1.1.3-gke.0.
May 16, 2019
April 05, 2019
Istio 1.0.6-gke.3 - Fixes a known security issue with the same fixes as OSS Istio version
1.0.7. New clusters will use this version by default when announced on the GKE security bulletins page, expected mid April 2019. If you create a new cluster with Istio on GKE before then, make sure to select a recommended GKE version to get this version of the add-on. Existing users should upgrade to the latest patched version of GKE as soon as possible.
Find out more in this security bulletin.
March 20, 2019
Istio 1.0.3-gke.3b - Fixes to all known issues in 1.0.3-gke.3a.
Istio 1.0.6-gke.1 - Fixes to all known issues in 1.0.3-gke.3a.
Istio 1.0.6-gke.1 - Upgrades Istio to version 1.0.6. See the Istio 1.0.6 release notes for more information.
January 28, 2019
Istio 1.0.3-gke.3a - Fixes to all known issues in 1.0.3-gke.0.
Istio 1.0.3-gke.3a - All ConfigMaps are now read-only, since these may change during upgrade.
Istio 1.0.3-gke.3a - Google Cloud's operations suite logging and tracing are enabled by default. However, please see the release issue below for current memory issues with tracing.
Istio 1.0.3-gke.3a - Istio on GKE's internal
prometheus (used for internal metrics) is renamed to
promsd to avoid confusion.
Istio 1.0.3-gke.3a - Google Cloud's operations suite tracing can consume too much memory in telemetry pods and should be disabled for now.
December 11, 2018
Istio 1.0.3-gke.0 - Depending on when the cluster was first created, may have a root certificate that will expire soon. Please follow the instructions to check the expiration date and, optionally, extend the life of your root certificate.
Istio 1.0.3-gke.0 - Updating an existing cluster Istio config between
PERMISSIVE doesn't work.
Istio 1.0.3-gke.0 - Setting the
--enable-stackdriver-kubernetes flag prevents the Istio Google Cloud's operations suite adapter from being installed, leading to no Google Cloud's operations suite metrics being published.
Istio 1.0.3-gke.0 - Mixer outputs logs to the local machine via the
stdio adapter by default, which can consume large amounts of CPU.
Istio 1.0.3-gke.0 - If you are using Google Cloud's operations suite with Istio 1.0.3 (the version used in this release of Istio on GKE for initial Istio installation), you can only use a single instance of Istio-Telemetry in your control plane. If you use multiple instances, telemetry data can be lost. To make sure your Google Cloud's operations suite support continues to work smoothly, do the following:
- Ensure only one instance of Istio-Telemetry is running by setting the
Istio-Telemetry HorizontalPodAutoscaler maxReplicasvalue to
kubectl edit -n istio-system HorizontalPodAutoscalers/istio-telemetry
- Make sure that your Istio-Telemetry resources are sufficient for one instance to handle the load from the entire cluster
kubectl edit -n istio-system Deployments/istio-telemetry