v1.9.4
3 minute read
Date: November 16, 2026
Breaking changes
- The jwt_authn requirement generated from a JWT
SecurityPolicyis now named after the SecurityPolicy that applies to the route,<namespace>/<name>, or for a merged policy after the route and parent policies it was built from,<route namespace>/<route name>+<parent namespace>/<parent name>, instead of the provider names and a hash of its content (<provider>[-or-<provider>...][-missing|-missing-or-failed]_<hash>). If the full policy-derived name exceeds 256 characters, the requirement name is its first 239 characters followed by_and the first 16 lowercase hexadecimal characters of the SHA-256 digest of the full, untruncated name, for a total of 256 characters. This applies to both single and merged policy names. Routes that share a policy still share one requirement. AnEnvoyPatchPolicythat targets a requirement by its old hash-based name needs to use the new name, including this truncation and hash suffix when applicable. The names change once on upgrade, so requests on connections opened before it may be refused with 403Wrong requirement_nameuntil those connections drain.
Security updates
- Bumped Envoy to v1.39.6.
New features
Bug fixes
- Fixed ExtensionServerPolicies that target a Gateway being attached to the listeners of every Gateway in the GatewayClass when
mergeGatewaysis enabled, andsectionNamematching same-named listeners on other Gateways. - Fixed the default Envoy proxy version reported by
envoy-gateway versionmissing the image digest. - Fixed requests on existing connections being refused with 403
Wrong requirement_nameafter a JWT SecurityPolicy edit. Since v1.9.0 the jwt_authn requirement was named after a hash of its content, so an edit of the JWT config (an audience, the JWKS,claimToHeaders,optional) renamed it in both the listener’srequirement_mapand every route’srequirement_name, and Envoy applies the two as separate updates. The requirement is now named after the SecurityPolicy that applies to the route, so such an edit changes only the listener’s requirement content. Connections that are still draining verify against the previous config until they close, as they did before v1.9.0. - Fixed status updates being dropped when the API server returned a timeout, throttling or another transient error. The status writer now retries these errors with backoff, in addition to conflicts.
- Fixed the status updater skipping a status write as unchanged when its cache had not yet seen its own previous write, which could leave a resource with an outdated status, for example a GatewayClass keeping the observedGeneration of its previous generation.
- Fixed the shutdown manager failing to return an HTTP response when the shutdown readiness wait exceeds the server write timeout.
- Fixed
egctl x translateand the file provider (standalone mode) silently ignoring ListenerSets in YAML input, which also dropped every route attached to them. ListenerSets loaded from files are now translated and programmed as in Kubernetes. - Fixed
egctl x translatefailing every OIDC SecurityPolicy withHMAC secret /envoy-oidc-hmac not found, which also replaced the targeted routes with a 500 direct response. egctl now looks up the HMAC Secret in the namespace given by--namespace(defaultenvoy-gateway-system). - Fixed ClusterTrustBundle references failing on Kubernetes 1.37+, where only
certificates.k8s.io/v1is served. Envoy Gateway now preferscertificates.k8s.io/v1and falls back tocertificates.k8s.io/v1beta1on older clusters. Updates to a referenced ClusterTrustBundle’strustBundle, such as CA rotation, now trigger a reconcile. - Fixed endpoint changes of Services referenced only by a SecurityPolicy’s OIDC provider backendRefs not being reconciled, which left Envoy calling a stale token endpoint IP.
Performance improvements
Deprecations
Other changes
- Bumped ratelimit to
3dfe2f9a. - Bumped Go from 1.26.10 to 1.26.11.
- Updated Go dependencies and the Envoy Gateway container base images.
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.