Announcing Istio 1.7.5
Istio 1.7.5 patch release.
This release contains bug fixes to improve robustness. This release note describes what’s different between Istio 1.7.4 and Istio 1.7.5
BEFORE YOU UPGRADE
Things to know and prepare before upgrading.
DOWNLOAD
Download and install this release.
DOCS
Visit the documentation for this release.
SOURCE CHANGES
Inspect the full set of source code changes.
Changes
Fixed pilot agent app probe connection leak. (Issue #27726)
Fixed how
install-cni
appliesistio-cni
plugin configuration. Previously, new configurations would be appended to the list. This has been changed to remove existingistio-cni
plugins from the CNI config before inserting new plugins. (Issue #27771)Fixed when a node has multiple IP addresses (e.g., a VM in the mesh expansion scenario). Istio Proxy will now bind inbound listeners to the first applicable address in the list rather than to the last one. (Issue #28269)
Fixed Istio to not run gateway secret fetcher when proxy is configured with
FILE_MOUNTED_CERTS
.Fixed multicluster
EnvoyFilter
to have valid configuration following the underlying changes in Envoy’s API. (Issue #27909)Fixed an issue causing a short spike in errors during in place upgrades from Istio 1.6 to 1.7. Previously, the xDS version would be upgraded automatically from xDS v2 to xDS v3. This caused downtime with upgrades from Istio 1.6 to Istio 1.7. This has been fixed so that these upgrades no longer cause downtime. Note that, as a trade off, upgrading from Istio 1.7.x to Istio 1.7.5 still causes downtime in any existing 1.6 proxies; if you are in this scenario you may set the
PILOT_ENABLE_TLS_XDS_DYNAMIC_TYPES
environment variable to false in Istiod to retain the previous behavior. (Issue #28120)Fixed missing listeners on a VM when the VM sidecar is connected to
istiod
but aWorkloadEntry
is registered later. (Issue #28743)
Upgrade Notice
When upgrading your Istio data plane from 1.7.x (where x < 5) to 1.7.5 or newer, you may observe connectivity issues between your gateway and your sidecars or among your sidecars with 503 errors in the log. This happens when 1.7.5+ proxies send HTTP 1xx or 204 response codes with headers that 1.7.x proxies reject. To fix this, upgrade all your proxies (gateways and sidecars) to 1.7.5+ as soon as possible. (Issue 29427, More information)