Announcing Istio 1.32.0
Istio 1.32 Release Announcement.
We are pleased to announce the release of Istio 1.32. Thank you to all our contributors, testers, users, and enthusiasts for helping us get the 1.32.0 release published! We would like to thank the Release Managers for this release, Jackson Greer from Microsoft, Jianpeng He from Tetrate, and Jack Kawell from Solo.io.
CHANGE NOTES
Get a detailed list of what's changed.
BEFORE YOU UPGRADE
Things to know and prepare before upgrading.
DOWNLOAD
Download and install this release.
DOCS
Visit the documentation for this release.
What’s new?
Gateway API
AuthorizationPolicytargetingHTTPRoute. As an experimental feature,AuthorizationPolicycan now target Gateway APIHTTPRouteresources viatargetRefs, soALLOWandDENYrules apply only to traffic matched by that route.- TLS tuning on gateways. TLS-terminating gateways can override the advertised ALPN protocols with
alpnProtocolsand configure ECDH curves withecdhCurves. - Experimental
XBackendsupport for describing how clients must connect to specific destinations. agentgatewaynow honors Gateway API frontend client certificate validation.
Ambient mode
- One east-west gateway for mixed meshes. An
istio-east-westgateway can now also serve sidecar multi-network traffic through anAUTO_PASSTHROUGHlistener on port 15443, so a mesh with both ambient and sidecar workloads no longer needs a separate east-west gateway for sidecars in each cluster. This requiresAMBIENT_ENABLE_MULTI_NETWORK.
Traffic management
- Utilization-based load balancing. A new
backendUtilizationpolicy onDestinationRuleuses backend-reported ORCA load reports to send fewer requests to busier endpoints. - Richer outlier detection.
DestinationRule.OutlierDetectionaddsoutlierDetectionHttpErrorCodes, to choose which HTTP status codes count as errors, andfailurePercentageThreshold, to eject hosts based on failure rate. - Configurable inbound retries. The new
defaultInboundHttpRetryPolicymesh config field configures, or disables with{}, the default retry policy on sidecar inbound routes. EnvoyFiltertransport socket matching. Filter chain matches can now select bytransportSocket, so patches precisely target chains that terminate TLS.- Mesh-wide
ProxyConfigwith selectors.ProxyConfigresources with workload selectors in the root namespace now apply to matching workloads in all namespaces.
Security
presencefor JWT rules.RequestAuthenticationjwtRulescan be markedREQUIRED, rejecting requests that are missing that token even when other rules are satisfied.PILOT_DISABLE_SELF_SIGNED_CAmakes istiod fail to start its CA instead of generating or reusing a self-signed root.
Telemetry
- Native Prometheus histograms.
pilot-agent’s metrics merger passes through the Prometheus protobuf format when scrapers request it, with a newistio_agent_scrape_format_totalcounter reporting the negotiated format.
Plus much more
- Headless TCP services can opt in to a single wildcard listener instead of one listener per pod IP
IST0178analyzer warning when anEnvoyFilterinserts an HTTP filter alongside anAuthorizationPolicythat targets anHTTPRouteServiceEntryvalidation warnings for catch-all and very broad addresses- Kubernetes API client timeouts in Istio components, configurable via
ISTIO_KUBE_HEADER_TIMEOUTandISTIO_KUBE_REQUEST_TIMEOUT GOMAXPROCSremoved from all charts, since Go now sets it from CPU limits automatically
Read about these and more in the full release notes.
Upgrading to 1.32
We would like to hear from you regarding your experience upgrading to Istio 1.32. You can provide feedback in the #release-1_32 channel in our Slack workspace.
Would you like to contribute directly to Istio? Find and join one of our Working Groups and help us improve.