Back to Devoured - November 13, 2026
DEVOURED
Announcing Istio 1.32.0

Announcing Istio 1.32.0

DevOps Istio
Istio 1.32.0 expands its Gateway API support and introduces utilization-based load balancing using backend-reported metrics.
What: This release supports Kubernetes 1.33 through 1.37. Key features include experimental AuthorizationPolicy targeting for HTTPRoute, new TLS tuning options on gateways, and utilization-based load balancing via the ORCA protocol.
Why it matters: The shift toward native Gateway API support and utilization-aware routing shows Istio's ongoing efforts to align with broader Kubernetes standards while improving performance in heterogeneous environments.
Decoder
  • Gateway API: An evolving standard for managing service networking in Kubernetes, intended as a more flexible successor to the original Ingress resource.
  • ORCA: A protocol that allows backends to report load information to the service mesh to optimize traffic distribution.
Original article

Announcing Istio 1.32.0

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.

What’s new?

Gateway API

  • AuthorizationPolicy targeting HTTPRoute. As an experimental feature, AuthorizationPolicy can now target Gateway API HTTPRoute resources via targetRefs, so ALLOW and DENY rules apply only to traffic matched by that route.
  • TLS tuning on gateways. TLS-terminating gateways can override the advertised ALPN protocols with alpnProtocols and configure ECDH curves with ecdhCurves.
  • Experimental XBackend support for describing how clients must connect to specific destinations.
  • agentgateway now honors Gateway API frontend client certificate validation.

Ambient mode

  • One east-west gateway for mixed meshes. An istio-east-west gateway can now also serve sidecar multi-network traffic through an AUTO_PASSTHROUGH listener 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 requires AMBIENT_ENABLE_MULTI_NETWORK.

Traffic management

  • Utilization-based load balancing. A new backendUtilization policy on DestinationRule uses backend-reported ORCA load reports to send fewer requests to busier endpoints.
  • Richer outlier detection. DestinationRule.OutlierDetection adds outlierDetectionHttpErrorCodes, to choose which HTTP status codes count as errors, and failurePercentageThreshold, to eject hosts based on failure rate.
  • Configurable inbound retries. The new defaultInboundHttpRetryPolicy mesh config field configures, or disables with {}, the default retry policy on sidecar inbound routes.
  • EnvoyFilter transport socket matching. Filter chain matches can now select by transportSocket, so patches precisely target chains that terminate TLS.
  • Mesh-wide ProxyConfig with selectors. ProxyConfig resources with workload selectors in the root namespace now apply to matching workloads in all namespaces.

Security

  • presence for JWT rules. RequestAuthentication jwtRules can be marked REQUIRED, rejecting requests that are missing that token even when other rules are satisfied.
  • PILOT_DISABLE_SELF_SIGNED_CA makes 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 new istio_agent_scrape_format_total counter 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
  • IST0178 analyzer warning when an EnvoyFilter inserts an HTTP filter alongside an AuthorizationPolicy that targets an HTTPRoute
  • ServiceEntry validation warnings for catch-all and very broad addresses
  • Kubernetes API client timeouts in Istio components, configurable via ISTIO_KUBE_HEADER_TIMEOUT and ISTIO_KUBE_REQUEST_TIMEOUT
  • GOMAXPROCS removed from all charts, since Go now sets it from CPU limits automatically

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.

Explore all 57 articles in today's digest

Fresh dev news, AI-digested daily. Never miss a trend at devoured.fyi