Principle:Kserve Kserve Model Promotion Rollback

Knowledge Sources	Blue-Green Deployment KServe Canary
Domains	MLOps, Deployment_Strategy, Reliability
Last Updated	2026-02-13 00:00 GMT

Overview

A deployment control pattern that either promotes a validated canary to serve 100% traffic or rolls back to the previous stable version.

Description

Model Promotion/Rollback is the terminal decision in a canary rollout:

• Promote: Remove canaryTrafficPercent from the spec, making the canary the new default with 100% traffic. The old revision scales to zero.
• Rollback: Set canaryTrafficPercent: 0, routing 100% traffic back to the previous stable revision. The canary revision is retained but receives no traffic.

The status propagation system tracks revision history via LatestRolledoutRevision and PreviousRolledoutRevision.

Usage

Use promotion after the canary has been validated at a sufficient traffic level. Use rollback if the canary shows degraded accuracy, increased latency, or errors at any point during progressive rollout.

Theoretical Basis

# Promotion/Rollback model (NOT implementation code)
Promote:
  - Remove canaryTrafficPercent field
  - Result: 100% traffic to latest revision
  - Previous revision scales to 0
  - LatestRolledoutRevision updated

Rollback:
  - Set canaryTrafficPercent: 0
  - Result: 100% traffic to previous revision
  - Canary revision retained but idle
  - PreviousRolledoutRevision serves all traffic

Status tracking (PropagateStatus):
  LatestRolledoutRevision = revision serving >=100% traffic
  PreviousRolledoutRevision = the prior LatestRolledoutRevision

Related Pages

Implemented By

• Implementation:Kserve_Kserve_Revision_Status_Propagation