LoginSign Up
← Back to all sparks
A

Argo Rollouts

INFRA · APIS
Velocity0.0

Progressive delivery controller for Kubernetes deployments

argo-rollouts.readthedocs.io ↗

An RC-only feed where 1.9's headline change was reverted before it shipped.

progressive-deliveryrelease-candidateshpanotificationskubernetes
◆Current state
Every entry in this window is a release candidate; no GA tag appears at all. The 1.9 line spent three RCs largely on pipeline problems — rc3 explicitly ships no changes from rc2 — and its one architectural change was withdrawn. That change would have narrowed .status.selector to report only the stable ReplicaSet for traffic-routed canaries so HPA stopped counting canary pods in its desired-replica math. The 1.10.0-rc1 notes are dominated by build and dependency work.
◆Where it's heading
The visible direction is operational rather than behavioural: notifications broadened to Teams workflows and NATS.io, a build system parameterized for company forks, CI skipped for docs-only changes, a move to pnpm. The selector revert says the project would rather live with awkward HPA math than break autoscaling for existing users, so progressive-delivery mechanics stay where they are.
◆Prediction
1.10.0 looks likely to land close to rc1 — dependency, CVE and notification work with no controller-semantics change — and the HPA selector question stays open unless it returns behind an opt-in flag.

◆Recent moves

  1. 1mo ago

    v1.10.0-rc1: notification targets, pnpm migration, CVE fix

    The 1.10 candidate is maintenance-shaped: CVE-2026-35469 addressed, expr and actions bumped, the UI moved to pnpm, and the notification engine extended to Teams workflows and NATS.io. The one forward-looking item is a build system parameterized for company forks.

    View source ↗
  2. 8mo ago

    v1.9.0-rc3: re-cut after a release pipeline failure

    Explicitly no changes from rc2 — the tag exists because the release pipeline failed. Nothing to evaluate beyond the fact that cutting 1.9 took three attempts.

    View source ↗
  3. 8mo ago

    v1.9.0-rc1 proposes, then withdraws, a selector change for HPA

    The notes lay out a change to report only the stable ReplicaSet in .status.selector so HPA stops averaging canary pods into its metric, then state it was reverted and will not ship in 1.9. Read it as the project's stated understanding of the HPA interaction, not as behaviour to rely on.

    View source ↗
  4. 8mo ago

    v1.9.0-rc2 skips analysis runs with no templates

    A single controller fix: analysis runs are skipped when no templates are specified. The rest of rc2's significance is what it removed — the reverted selector change.

    View source ↗