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 ↗

One status-churn fix, shipped to four maintenance branches inside forty minutes.

api-gatewaykubernetes-gateway-apimulti-branch-backportsenvoytranslation-correctnessfeature-flags
◆Current state
Gloo maintains four release lines at once — 1.18, 1.19, 1.20 and 1.21 — plus a 1.22 beta series, and fixes are fanned across all of them together. On 5 August, v1.18.41, v1.19.20, v1.20.22 and v1.21.13 were cut within forty-five minutes of each other carrying the same Kubernetes Gateway report-churn fix and the same Go, gRPC and kubectl dependency bumps.
◆Where it's heading
The recurring theme is translation correctness under Kubernetes Gateway API — specifically, bugs where the translator's internal state does not behave the way its callers assume. The report-churn fix found equality checks comparing maps of pointer values, so identical output registered as changed on every recompute. The delegateOptions fix in beta11 found RouteOptions assigned by reference from the snapshot, so merging parent Virtual Service options mutated shared protos and contaminated every other route for the rest of the cycle. Both ship with the same instinct for caution: the second one is gated behind GLOO_ISOLATE_DELEGATE_ROUTE_OPTIONS so operators can revert.
◆Prediction
The 1.22 beta line will keep collecting Gateway API translation fixes ahead of a stable release, and each one that matters will be backported across all four maintenance branches on the same day, as this window shows twice.

◆Recent moves

  1. 2d ago

    Gloo 1.20.22 stops no-op Kubernetes Gateway report churn

    Carries the report-churn fix to the 1.20 line: equality checks compared maps of pointer values so identical translation output was reported as changed on every recompute, and status rendering wrote default conditions back into the objects being compared. Reports now compare semantically and status rendering is read-only.

    View source ↗
  2. 2d ago

    Gloo 1.21.13 adds hostRewriteLiteral, reverts admission validation

    The most substantive of the four same-day releases: alongside the dependency bumps it adds hostRewriteLiteral to the shadowing plugin for rewriting the Host header on mirrored requests, and reverts upstream admission validation in Gateway API mode after its breaking behavior was judged to need more consideration.

    View source ↗
  3. 2d ago

    Gloo 1.18.41 backports the Gateway report-churn fix

    The same report-churn fix and dependency set backported to the 1.18 line, cut forty minutes after the 1.20 release. Identical content, older branch — evidence of how far back solo.io still supports this product.

    View source ↗
  4. 2d ago

    Gloo 1.19.20 backports the Gateway report-churn fix

    The 1.19 instance of the same 5 August backport, released four minutes after the 1.18 one. Same fix, same bumps, different branch.

    View source ↗
  5. 5d ago

    Gloo 1.22.0-beta12 adds hostRewriteLiteral to shadowing

    A single-feature beta adding hostRewriteLiteral to the shadowing plugin, so mirrored traffic can carry a different Host header than the original request. It reached the 1.21 stable line three days later.

    View source ↗
  6. 7d ago

    Gloo 1.22.0-beta11 isolates delegated RouteOptions before merging

    Fixes a translator bug where RouteOptions referenced through delegateOptions were assigned by reference from the snapshot, so merging parent Virtual Service options mutated the shared proto and contaminated every other route using it for the remainder of the cycle. Cloning is now the default, with GLOO_ISOLATE_DELEGATE_ROUTE_OPTIONS available to restore old behavior. Helm gains explicit Deployment or DaemonSet workload selection.

    View source ↗