Reported by InfoQ on November 16, 2026.
Envoy Gateway 1.9.1 is a maintenance release focused on security, upgrade reliability and controller behavior. Its most consequential change reverses a timeout setting introduced in 1.9.0: the initial fetch timeout for Secret Discovery Service (SDS) and Route Discovery Service (RDS) returns to Envoy’s default of 15 seconds, matching the behavior in 1.8.x.
According to the report, setting the timeout to zero could leave clusters waiting indefinitely for missing Secrets or Endpoints. A cluster stuck warming could block Cluster Discovery Service (CDS) updates and delay health checks.
The upgrade path depends on the version already running. The project recommends that 1.8.x users skip 1.9.0 and upgrade directly to 1.9.1. For existing 1.9.0 deployments, Envoy Gateway warns that changing SDS configuration during a controller upgrade can trigger an Envoy issue affecting proxies still running as the new controller is deployed. In affected cases, TLS listeners may become active without certificates, causing new TLS handshakes to fail. Backend TLS and global rate-limit services may encounter similar certificate or CA problems.
Envoy Gateway recommends a rolling-update configuration to replace proxy Pods quickly, provided the cluster has enough capacity. Pod replacement can interrupt existing connections, particularly long-lived WebSocket and gRPC connections. Separately, a production user reported in a GitHub issue that long-running Envoy proxies lost their downstream TLS certificates and stopped serving HTTPS until manually restarted. The user linked the outage to changes in 1.9.0; the report does not establish that account as a confirmed cause of every affected deployment.
The release also enables AES-256-GCM for OAuth2/OIDC session-cookie encryption and removes the older AES-256-CBC decryption path to address the padding-oracle vulnerability identified as CVE-2026-47775. Users with sessions encrypted by the old mechanism will need to authenticate again after upgrading. Deployments with custom Envoy bootstrap configurations must explicitly set the corresponding runtime configuration.
Other security changes add validation for OIDC issuer URLs and remove an implicit fallback from HTTPS to HTTP when pulling OCI Wasm images. HTTP remains available when a registry is explicitly configured as insecure. The previous fallback could have allowed an on-path attacker to supply arbitrary Wasm code. The release also fixes a security-context issue involving tenant-supplied EnvoyProxy configurations that could remove hardened restrictions, including limits on privileged execution or running as root.
Operational fixes include scoping OIDC cookies to the redirect path, reacting to namespace-label changes without restarting the controller, and addressing hostname conflicts, crashes when an optional CRD is absent, and incorrect consistent-hashing configuration for UDP routes. Global rate limiting now uses Endpoint Discovery Service (EDS) to obtain Kubernetes Service and EndpointSlice information, while retaining DNS-based behavior if the service or Endpoints cannot be discovered. New per-phase tracing spans for Gateway API and xDS translation help operators locate time spent processing listeners, routes, policies, extension hooks and xDS validation.
Source: infoq.cn (originally published 2026-11-16 17:06 UTC+8)