flagger

mirror of https://github.com/fluxcd/flagger.git synced 2026-09-05 02:47:17 +00:00

Files

T

Pedram Pourmohammad 8eaa0408af Keep canary alive when primary promotion fails

When the canary analysis succeeds, Flagger copies the canary pod spec
to the primary and waits for the primary rollout to finish. If the
primary fails to become ready, the non-retriable readiness error
triggered the standard analysis rollback, which routes all traffic to
the primary and scales the canary to zero.

During promotion the primary already runs the new (failing) spec while
the canary is the only healthy copy of the new revision still serving
traffic. Rolling back therefore sends all traffic to the broken primary
and deletes the working canary, taking the application down.

Halt the promotion instead: when the primary is not ready and the canary
is in the Promoting or Finalising phase, mark the rollout as failed and
alert, but keep the canary running and leave routing untouched until the
primary recovers or a corrected revision is applied.

Fixes #1898

Signed-off-by: Pedram Pourmohammad <eragon.pedy@gmail.com>

2026-06-27 19:56:03 +03:30

controller_test.go

fix: default namespace for cross-namespace ref validation

2025-10-08 09:16:29 +02:00

controller.go

fix: default namespace for cross-namespace ref validation

2025-10-08 09:16:29 +02:00

events_test.go

Release loadtester 0.36.0

2025-10-16 13:34:13 +03:00

events.go

Release Flagger 1.42.0