Automated Progressive Traffic Shifting
Quick Reference
What & Why
Definition
>= 70% of deployments use automated traffic shifting with SLO monitoring at each phase (Flagger, Argo Rollouts).
Business Value
Reduces deployment risk by 85% and enables automatic rollback within 60 seconds of anomaly detection through canary deployments and metric monitoring Achieving >= 70% deployments have automated traffic control is a key milestone toward this goal.
Context
This capability is part of the Acceleration milestone's focus on scale automation, embed compliance, improve speed & reliability. Essential for teams targeting DF, MTTR improvements.
Success Criteria
>= 70% deployments have automated traffic control
Measurement
Automated traffic shifting adoption rate
Evidence
- Flagger/Argo Rollouts config
- Traffic shift metrics
- SLO compliance during rollouts
In Practice
Real-World Implementation
System automatically shifts traffic in phases (5%, 25%, 50%, 100%), monitors SLOs (error rate, latency) at each phase, auto-rollback if SLO breached.
Concrete Example
Implementation Guide
Prerequisites
Implementation Steps
Follow the measurement approach: Automated traffic shifting adoption rate
For detailed step-by-step guidance, refer to the Progressive Delivery & Advanced Deployment Implementation Kit.
Resources
Implementation Kit
Progressive Delivery & Advanced Deployment KitTemplates
Browse all templatesRelated Resources
View learning pathsRelated Capabilities
Prerequisites
Implement these first
Enables
What this unlocks
Complementary
Often adopted together, from the Progressive Delivery & Advanced Deployment epic
Troubleshooting & FAQs
Common Issues
Issue: Target metric not improving
Solution: Verify measurement is accurate, check if prerequisites are fully implemented, review evidence artifacts for completeness
Issue: Team resistance to adoption
Solution: Start with pilot team, demonstrate value with metrics, provide training and support during transition
Issue: Inconsistent implementation across teams
Solution: Create shared templates and guidelines, establish regular sync meetings, use automation to enforce standards
Frequently Asked Questions
Can we implement this before completing prerequisites?
While possible, it's not recommended. Prerequisites ensure foundational practices are in place, making this capability more effective and easier to adopt.
How long does implementation typically take?
Most capabilities can be implemented within 90 days when tackled as part of the Acceleration milestone. Individual timelines vary based on team size and existing practices.