# Argo Rollouts 1.11 Separates Automation Time From Approval Delay

- Link: https://thestackobserver.com/argo-rollouts-1-11-separates-automation-time-from-approval-delay/
- Published: 2026-11-20T11:58:29-05:00
- Author: Stackxx

Progressive delivery has always promised a safer way to ship: expose a small slice
of traffic, measure the result, and expand only when the evidence looks good. Yet
many platform teams still struggle to answer a basic operational question: how long
does a rollout actually take? A deployment may appear to need 42 minutes, while 
only 12 of those minutes belong to automation and the remaining 30 are a manual 
approval pause. Without that distinction, teams optimize the wrong part of the system.

Argo Rollouts 1.11’s release candidate addresses that blind spot with first-class
rollout duration tracking. Each Rollout can record when an update started, when 
it finished, how long it spent waiting at manual pauses, and how it completed. The
controller also exposes Prometheus histograms for total duration, active progression
time, and manual pause time. The important change is not merely three more metrics.
It is a cleaner model of delivery latency that separates machine time from decision
time.

For platform engineering teams, that separation creates a practical operating loop:
measure the stages independently, assign each delay to the team that can influence
it, and improve safety without treating every pause as waste. Because 1.11 is still
a release candidate, teams should test the model now and use the results to prepare
dashboards and service-level objectives before adopting it broadly.

## One rollout duration hides three different systems

A single wall-clock number combines several behaviors that have different owners.
The deployment controller reconciles resources and shifts traffic. Analysis providers
query metrics and evaluate conditions. People may inspect evidence and click promote.
Cluster capacity, image pulls, readiness checks, monitoring query latency, and approval
policy can all contribute to the same elapsed duration.

Argo Rollouts 1.11 makes that composite visible through three Prometheus histograms.**
rollout_duration_seconds** measures the full interval, including pauses. **rollout_progression_duration_seconds**
measures active progression without manual pauses. **rollout_manual_pause_duration_seconds**
measures the time spent waiting for a person, including explicit pause steps, blue-
green deployments without automatic promotion, and inconclusive analyses.

The status for an individual Rollout also records its start and finish timestamps,
total manual pause duration, and completion status. The published completion labels
include outcomes such as Promoted, FastPromoted, Aborted, Superseded, RolledBack,
and FastRolledBack. That outcome dimension matters: a fast successful rollout, a
fast abort, and a rollout superseded by another change are not equivalent delivery
results.

This is the central operational value of the release. Teams no longer need to infer
human wait time from event streams or build custom instrumentation around every 
pause. They can compare total time with active time and ask a more useful question:
_which part of our delivery system is consuming the interval?_

## Start with a dashboard that preserves the distinction

The first implementation mistake would be to collapse the new signals back into 
one percentile. A useful dashboard should display total duration, active progression
duration, and manual pause duration side by side for the same window. Show at least
the median and a tail percentile such as p90 or p95. Averages can hide the few rollouts
that wait for hours and dominate developer frustration.

Segment the views by the dimensions that correspond to an operational decision. 
Environment is usually the first split because production approval policy differs
from staging. Application or owning team helps identify outliers, while completion
status separates normal promotions from recovery paths. Avoid adding so many labels
that metric cardinality becomes its own reliability problem. Begin with the labels
already exposed by the controller and add context in dashboards or recording rules
where possible.

A practical dashboard can answer four questions:

 * **How long do successful rollouts take end to end?** Use total duration filtered
   to promoted outcomes.
 * **How much of that time is automated progression?** Compare progression duration
   with total duration over the same population.
 * **Where do humans wait longest?** Rank applications or environments by manual
   pause duration at the tail.
 * **Do slow rollouts correlate with bad outcomes?** Compare promoted, aborted, 
   rolled-back, and superseded distributions rather than mixing them.

Do not treat every long rollout as a defect. A deliberate observation window may
be the safety mechanism that catches a slow-burning regression. The dashboard should
help distinguish an intentional canary soak from an accidental queue for approval.
Document expected pauses in the rollout template so that operators can interpret
the chart in context.

## Define objectives for active time and decision time separately

A single deployment SLO can create harmful incentives. If teams are measured only
on total duration, they may shorten observation windows or automate approvals before
their telemetry is trustworthy. If they are measured only on controller speed, users
may still wait hours for a promotion. The metrics in 1.11 support separate objectives
for two distinct systems.

For active progression, set a target that covers the controller’s work, workload
readiness, traffic routing, and automated analysis. For manual pauses, define an
expectation based on the risk and environment. A staging rollout might be expected
to auto-promote. A production rollout for a high-impact service might legitimately
require a 15-minute observation and an approval within a defined response window.

Example objectives could state that 95% of successful staging rollouts complete 
active progression within 10 minutes, while 90% of production approvals occur within
20 minutes during supported hours. Those numbers are illustrative; teams should 
establish a baseline before choosing thresholds. The key is that a missed active-
time objective points toward automation, infrastructure, or analysis. A missed pause-
time objective points toward ownership, notification, policy, or staffing.

Track aborted and rolled-back outcomes alongside the objectives. Faster is not better
if the change failure rate rises. The most valuable trend is a reduction in avoidable
latency while successful outcomes remain stable or improve.

## Use the metrics to investigate, not to assign blame

Duration data becomes counterproductive when it is turned into a simplistic team
leaderboard. Applications differ in traffic shape, readiness behavior, regulatory
constraints, and blast radius. The numbers are better used as the entrance to an
investigation than as a universal productivity score.

### When active progression is slow

Inspect the rollout steps and correlate them with Kubernetes events, pod startup
latency, image pull time, scheduler pressure, service-mesh propagation, and analysis-
provider query latency. A long progression interval may reveal oversized images,
insufficient cluster headroom, readiness probes that mask startup work, or metric
queries whose windows are longer than necessary. It may also reveal an appropriate
soak period, in which case the correct action is to document it rather than remove
it.

### When manual pause time is slow

Check whether the right owner receives a notification with enough context to decide.
An approval that requires opening five dashboards and reconstructing the change 
will remain slow even if the alert arrives instantly. Promotion messages should 
link to the diff, rollout state, analysis results, relevant service-level indicators,
and the runbook. Define escalation behavior for unattended pauses and clarify whether
an inconclusive analysis requires a human decision or an automatic abort.

### When aborted rollouts are unusually fast or slow

A fast abort can signal effective automated detection, but it can also indicate 
a noisy threshold. A slow abort may expose a weak signal, an analysis interval that
is too coarse, or a recovery path that waits for manual action. In Argo Rollouts
1.11, fixes to abort behavior with dynamic stable scaling are also relevant: the
project says traffic now returns to the stable version before the canary scales 
down in a scenario that could previously become stuck. Test recovery timing as seriously
as promotion timing.

## Run a controlled evaluation of the release candidate

Because version 1.11 is an RC, adopt it as an evaluation rather than a fleet-wide
upgrade. Choose representative services that cover canary and blue-green strategies,
automatic and manual promotion, and at least one abort path. Capture a baseline 
from the existing controller events or deployment records so the new measurements
can be checked against known rollout histories.

The evaluation should include these steps:

 * Install the release candidate in a non-production cluster or isolated controller
   scope and confirm compatibility with your Kubernetes version and traffic provider.
 * Exercise successful promotion, manual promotion, fast promotion, abort, rollback,
   and superseded-change scenarios.
 * Verify that status timestamps and completion states match the observed sequence
   for each test.
 * Scrape the three histograms, inspect their buckets and labels, and estimate the
   additional time-series cardinality before setting long retention.
 * Build recording rules for the percentiles and ratios that operators will actually
   use instead of placing expensive raw queries on every dashboard.
 * Compare the measured manual pause duration with explicit pause steps and inconclusive
   analysis behavior in your templates.

Teams using the Web metric provider should add a specific compatibility test. The
1.11 announcement notes that plain-text and empty responses are now evaluated against
success and failure conditions; earlier behavior could report such responses as 
successful without evaluating those conditions. An AnalysisTemplate that previously
passed may fail after the upgrade. Review every Web provider template that consumes
plain text or an empty body, and test both expected and malformed responses.

Also confirm the dashboard’s network binding if upgrading from older patch levels.
The project notes that the dashboard defaults to localhost in patched releases addressing
a security issue. Operators who intentionally expose it through a Kubernetes Service
need an explicit address configuration and should preserve appropriate authentication
and network controls.

## Make duration part of the platform contract

Once the measurements are trusted, add them to the platform’s paved road. Provide
a default dashboard, alerting rules for stuck or extreme rollouts, and template 
guidance for intentional observation windows. Include ownership metadata so an unattended
pause reaches the correct team. Offer standard analysis templates that produce decisive
signals and make their expected evaluation time visible.

Platform documentation should explain what each interval includes, which outcomes
are counted, and how teams should interpret a superseded or fast-promoted rollout.
This prevents local dashboards from redefining the metrics in incompatible ways.
It also gives application teams a common vocabulary: controller progression, automated
analysis, planned observation, and human decision are separate pieces of the path.

The broader lesson from Argo Rollouts 1.11 is that deployment speed is not one number.
Progressive delivery is a socio-technical control system, with automation and human
judgment sharing the clock. By measuring those parts independently, platform teams
can remove accidental waiting, protect intentional safety checks, and direct improvement
work toward the component that actually causes the delay.

## Sources

 * [Argo Project: Argo Rollouts 1.11 release candidate](https://blog.argoproj.io/argo-rollouts-1-11-release-candidate-943cc8de8696)
 * [GitHub: Argo Rollouts v1.11.0-rc1 release notes](https://github.com/argoproj/argo-rollouts/releases/tag/v1.11.0-rc1)
