← Back to all sparks
G

Gloo Gateway

INFRA · APIS
Velocity5.0

Envoy-powered API gateway and ingress controller for Kubernetes

Gloo Gateway is running four branches in parallel and shipping nothing but upkeep to all of them.

api-gatewaymaintenancekuberneteshelmbackports
Current state
Gloo Gateway is in pure maintenance across four supported lines — 1.18, 1.19, 1.20 and 1.21 — with releases landing in same-day batches that carry identical payloads. The last month produced Go and oras-go bumps, a Helm readiness-probe fix, and a revert of an admission-time upstream validation change that turned out to be breaking. The only additive change in the window was hostRewriteLiteral support in the shadowing plugin, and it landed on 1.21 alone.
Where it's heading
The release stream reads as a supported-branch treadmill rather than a development line: each fix is authored once and fanned out to every branch within twenty minutes. That the team reverted its own admission-validation change rather than gate it suggests a low tolerance for behavioral risk on these branches. New capability is being held back from the maintenance stream, so whatever is being built is not visible in this feed.
Prediction
Expect the same pattern to continue — paired dependency bumps and single-PR fixes replicated across 1.19 through 1.21, with any reworked upstream-validation behavior reappearing behind an opt-in rather than as a default.

Recent moves

  1. 19d ago

    SDS readiness probe can now be disabled or partially overridden

    The SDS container's readinessProbe now falls back to the chart default only when the value is unset, so operators can explicitly disable it or override one field without silently losing the rest. It is a small Helm change but it restores configuration control that the previous always-require behavior took away. This is the only non-dependency change in the current batch.

    View source ↗
  2. 19d ago

    Gloo 1.20.24 backports the SDS readiness probe fix

    Byte-identical to 1.21.15 — the same single-PR Helm probe fix backported to the 1.20 line. It carries no separate content of its own.

    View source ↗
  3. 19d ago

    Gloo 1.19.22 backports the SDS readiness probe fix

    The 1.19 branch's copy of the same readinessProbe fix, released nineteen minutes ahead of the 1.21 tag. Identical body, no branch-specific change.

    View source ↗
  4. 22d ago

    Gloo 1.19.21 is a Go and oras-go dependency bump

    Go moves to 1.25.13 and oras-go to 2.6.2, with nothing else in the release. Routine supply-chain upkeep on the 1.19 branch.

    View source ↗
  5. 22d ago

    Gloo 1.20.23 carries the same dependency bump as 1.19.21

    The 1.20 twin of the same dependency batch, tagged ninety seconds apart from the 1.19 release. No branch-specific content.

    View source ↗
  6. 22d ago

    Gloo 1.21.14 bumps Go to 1.26.6 and oras-go to 2.6.2

    The 1.21 line takes the same oras-go bump but a newer Go toolchain than its sibling branches. Dependency maintenance only.

    View source ↗