RATATOSK
← All releases

Istio1.30.5

Security 1Important fixes 9Other changes 2

Get Istio alerts

Email is sent weekly only when there are changes to check; critical security advisories are sent immediately.

Security1

Unsafe multicluster kubeconfig handling fixed in istioctl analyze

Affectssetups using istioctl analyze with Kubernetes clients built from istio-system multicluster secrets(Inferred)

Before this release, istioctl analyze built Kubernetes clients directly from kubeconfigs in those secrets, so a crafted secret could run an exec credential plugin or read local files through unsafe auth fields on the machine running istioctl. It now sanitizes those kubeconfigs before building clients, using the same sanitization as istiod.

Show release-note lines
- Fixed istioctl analyze building Kubernetes clients directly from istio-system
multicluster secrets without sanitizing the kubeconfig, which could allow a crafted
secret to run an exec credential plugin (or read local files via other unsafe auth
fields) on the machine running istioctl . The kubeconfig is now sanitized the same
way istiod already sanitizes these secrets.
Credit : This vulnerability was discovered and reported by Adam Korczynski.
istio.io/news/releases/1.30.x/announcing-1.30.5/

Important fixes9Silent failure1

  • Ambient-mode CNI redirect-rule duplication fixed
    Affectsambient-mode installations using the CNI node agent’s auto-detected iptables backend(Inferred)

    When the agent restarted and its auto-detected backend switched between nft and legacy, reconciliation could miss existing rules and add a second redirect ruleset to already-enrolled pods. The release fixes this behavior, but the note does not say whether it removes duplicate rules already written.

    - Fixed an issue in ambient mode where the CNI node agent’s auto-detected iptables backend
    ( legacy vs nft ) could flip between agent restarts, causing duplicate
    redirect rules to be written into already-enrolled pods.
    ( Issue #61020 )
    istio.io/news/releases/1.30.x/announcing-1.30.5/
  • MDS Address-only workload updates fixed
    AffectsEnvoy proxies subscribed to Workload metadata discovery (MDS) with AMBIENT_SCOPED_ADDRESS_PUSHES enabled

    With AMBIENT_SCOPED_ADDRESS_PUSHES enabled, the default, subscribed Envoy proxies did not receive incremental workload updates for Address-only changes.

    - Fixed an issue where Envoy proxies subscribed to Workload metadata discovery (MDS) did not
    receive incremental workload updates for Address-only changes when
    AMBIENT_SCOPED_ADDRESS_PUSHES was enabled (the default).
    istio.io/news/releases/1.30.x/announcing-1.30.5/
  • Random workload gateway selection fixed
    AffectsWorkloads on networks with more than one gateway entry

    Previously, the gateway could be selected in random order, causing unnecessary WDS pushes on every recompute and potentially alternating the workload’s gateway address.

    - Fixed an issue where the network gateway selected for a workload was picked in a random
    order when a network had more than one gateway entry, which caused unnecessary workload
    (WDS) pushes on every recompute and could cause a workload’s gateway address to alternate.
    istio.io/news/releases/1.30.x/announcing-1.30.5/
  • Sub-second precision truncation fixed in sidecar.istio.io/statsEvictionIntervalSilent failure
    Affectssetups using sidecar.istio.io/statsEvictionInterval with sub-second precision
    - Fixed the sidecar.istio.io/statsEvictionInterval annotation silently truncating
    sub-second precision.
    istio.io/news/releases/1.30.x/announcing-1.30.5/
  • ListenerSet status reporting fixed
    AffectsListenerSet resources

    Previously, the Accepted and Programmed conditions could remain True even when none of a ListenerSet’s listeners were usable. They now report False with reason ListenersNotValid.

    - Fixed ListenerSet status reporting so that a ListenerSet with no valid listeners now
    reports the Accepted and Programmed conditions as False with reason ListenersNotValid .
    Previously the ListenerSet-level conditions could remain True even when none of its listeners
    were usable.
    istio.io/news/releases/1.30.x/announcing-1.30.5/
  • ServiceEntry empty-selector matching fixed
    AffectsServiceEntry resources with a present but empty workload selector

    Previously, these resources matched every workload in their namespace. After the upgrade, they no longer do, though the resulting matching behavior is not specified.

    - Fixed ServiceEntries with a present but empty workload selector incorrectly matching all workloads in their namespace.
    istio.io/news/releases/1.30.x/announcing-1.30.5/
  • observedGeneration stale-value issue fixed
    Affectsresources with status updates

    When a resource was modified again while an earlier status write was queued, observedGeneration could remain stale. That stale-value issue is fixed.

    - Fixed observedGeneration getting stuck on a stale value when a resource is modified again
    while an earlier status write is still queued.
    istio.io/news/releases/1.30.x/announcing-1.30.5/
  • HTTP/2 restored for JWKS public-key fetches
    Affectsistiod JWKS fetches through HTTP CONNECT proxies

    Through some HTTP CONNECT proxies, JWKS fetches over HTTP/1.1 failed, causing JWT requests to be rejected; a corporate-proxy report recorded HTTP 404 responses. Re-enabling HTTP/2 fixes those fetches.

    - Fixed the JWKS resolver forcing all public-key fetches to HTTP/1.1. The custom
    TLSClientConfig and DialContext used for TLS pinning and CIDR blocking caused Go’s
    net/http to disable automatic HTTP/2, so ALPN never negotiated h2. HTTP/2 is now
    re-enabled (matching http.DefaultTransport ), fixing JWKS fetches that fail over HTTP/1.1
    through some HTTP CONNECT proxies.
    ( Issue #61250 )
    istio.io/news/releases/1.30.x/announcing-1.30.5/
  • sidecar.istio.io/statsFlushInterval startup failure fixed
    Affectssetups using the sidecar.istio.io/statsFlushInterval annotation with values of one minute or more or below one second

    At one minute or more, or below one second, the annotation produced an invalid Envoy bootstrap and prevented the proxy from starting. Those values no longer prevent the proxy from starting.

    - Fixed the sidecar.istio.io/statsFlushInterval annotation producing an invalid Envoy
    bootstrap for values of one minute or more, and for sub-second values, which prevented the
    proxy from starting.
    istio.io/news/releases/1.30.x/announcing-1.30.5/
Other changes2
  • Ambient CNI iptables backend detection stabilized
    Changes
    - Fixed an issue in ambient mode where the CNI node agent’s auto-detected iptables backend
    ( legacy vs nft ) could flip between agent restarts, causing duplicate
    redirect rules to be written into already-enrolled pods.
    ( Issue #61020 )
    istio.io/news/releases/1.30.x/announcing-1.30.5/
  • istiod caches serialized workloads for Envoy metadata
    ( Issue #61502 )
    - Fixed an issue where istiod repeatedly serialized the same workload when
    pushing workload metadata to Envoy proxies.
    istio.io/news/releases/1.30.x/announcing-1.30.5/

Summaries are produced by AI, so they can be wrong, and they are provided without warranty.