Repository navigation
Dependency Bumps
- solo-io/envoy-gloo has been upgraded to v1.36.13-patch1.
- golang/go has been upgraded to v1.26.11.
- containerd/containerd has been upgraded to v1.7.36.
- go-git/go-git has been upgraded to v5.19.2.
- open-telemetry/opentelemetry-go has been upgraded to v1.45.0.
- klauspost/compress has been upgraded to v1.20.2.
- golang.org/x/net has been upgraded to v0.62.0.
- klauspost/compress has been upgraded to v1.18.7.
- go-jose/go-jose has been upgraded to v4.1.6.
Fixes
- With watchNamespaceSelectors, a namespace or Settings change no longer restarts the gloo setup loop before the running setup has attempted its first xDS sync. The restart happens once that sync has run. GLOO_SETUP_FIRST_SYNC_TIMEOUT (default 10m) bounds the wait if the first sync never returns. Other components that share the setup loop are not affected. With endpointsWarmingTimeout set to 0s, gloo logs a warning at setup, since a setup run's first sync can then publish clusters with no endpoints. (solo-io/solo-projects#9349)
- When the gateway proxy reconcile fails, gloo still publishes xDS for the Proxies it lists, but no longer sends empty snapshots to connected Envoys whose Proxy is missing from that list. After a gloo pod restart the in-memory Proxy store is empty, so a failed first reconcile previously sent every connected Envoy an empty config. After an in-process setup re-run the store holds the previous run's Edge Proxies (next entry), so a failed first reconcile publishes those. (solo-io/solo-projects#9349)
- When a namespace matching watchNamespaceSelectors re-runs gloo setup, the new run's in-memory Proxy store now starts with the Gloo Edge Proxies the previous run wrote to the write namespace. The gateway reconciler keeps a previously written listener when its Gateway is newly rejected only if it can read the previous Proxy; with an empty store, the first reconcile after a re-run stripped the listener. No Edge Proxies are copied when the gateway controller is disabled. persistProxySpec=true is unchanged. (solo-io/solo-projects#9168)
- Retry proxy translation with capped exponential backoff, even when configuration does not change, after envoy validation is interrupted during xDS translation or a Gloo Edge proxy reconcile. Preserve the last good xDS snapshot until translation succeeds, and stop retrying on shutdown or proxy deletion. (solo-io/solo-projects#9168)