LoginSign Up
← Back to all sparks
G

Gloo Gateway

INFRA · APIS
Velocity5.0

Envoy-powered API gateway and ingress controller for Kubernetes

www.solo.io/products/gloo-gateway ↗

Gloo Gateway ports its restart and empty-config fixes to 1.21; 1.19 gets only dependency bumps.

api-gatewayenvoyxdsrate-limitingbackportsreliability
◆Current state
Gloo Gateway maintains the 1.19, 1.20 and 1.21 lines in parallel. The 13 November batch brings the 1.20 restart fixes to 1.21.20: setup no longer restarts before its first xDS sync, a failed reconcile stops sending empty configs to Envoys, the Proxy store survives a setup re-run, and translation retries with backoff while keeping the last good snapshot. 1.20.32 adds that retry logic to 1.20, and 1.19.28 is dependency updates only.
◆Where it's heading
Three weeks of releases have centred on one failure mode: what happens to live Envoy config when gloo restarts or a reconcile fails. Each patch narrows the window where proxies get empty or stale config, and the fixes now reach all three supported lines except 1.19.
◆Prediction
Expect the retry-and-keep-last-good-snapshot fix to be backported to 1.19 next, or 1.19 to stay on dependency bumps only; the entries do not show a new feature line.

◆Recent moves

  1. 1d ago

    1.21.20 waits for first xDS sync and stops empty Envoy configs

    The 1.21 line catches up with the 1.20 restart fixes in one release: no setup restart before the first sync, no empty snapshots to Envoys after a failed reconcile, Proxy state carried across setup re-runs, and rate-limit rules kept after namespace changes. It is the largest release in this run of patches.

    View source ↗
  2. 1d ago

    1.20.32 retries failed translation and keeps last good config

    When Envoy validation is interrupted, gloo now retries translation with capped backoff and keeps serving the last good snapshot until it succeeds. The fourth 1.20 patch in two weeks aimed at stopping config loss during restarts.

    View source ↗
  3. 1d ago

    1.19.28: Go 1.26.11, containerd and Helm dependency bumps

    Dependency updates only on the oldest maintained line, including Go 1.26.11 and Helm 3.18.5. None of the restart fixes in this batch reach 1.19.

    View source ↗
  4. 3d ago

    1.20.31 fixes vanishing rate limits and stale ext-auth again

    The second follow-up to 1.20.29's restart fix: rate-limit rules survive namespace changes, setup runs keep separate Proxy stores, and failed reconciles again push AuthConfig and Secret changes to ext-auth. It closes the gap where a deleted API key could keep working.

    View source ↗
  5. 6d ago

    1.19.27 bumps klauspost/compress to v1.18.7

    A single dependency bump on the oldest maintained line. No functional change.

    View source ↗
  6. 6d ago

    1.20.30 fixes vanishing rate limits and stale ext-auth secrets

    This release undoes side effects of 1.20.29's restart fix: setup runs get their own Proxy store again, rate-limit rules survive Settings changes, and ext-auth and rate-limit syncs run after a failed reconcile. Deleted API key Secrets now reach the ext-auth server again, which closes a security-relevant gap.

    View source ↗