Progressive Delivery

Purpose

Implement progressive delivery strategies: canary releases, blue-green deployments, feature flags in production, traffic mirroring, and automated rollback based on metrics. Progressive delivery reduces deployment risk by exposing changes to a subset of users before full rollout.

Agent Protocol

Trigger

Exact user phrases: "progressive delivery", "canary", "canary deployment", "canary release", "blue-green", "blue/green", "feature flag", "feature toggle", "traffic shifting", "traffic split", "A/B testing", "production testing", "Flagger", "Argo Rollouts", "rollout strategy", "gradual rollout", "percentage rollout", "automated rollback", "metrics-based promotion", "traffic mirroring", "shadow traffic".

Input Context

• Current deployment strategy (rolling update, recreate, manual)
• Service mesh or ingress controller (Istio, Linkerd, NGINX, Traefik)
• Metrics platform (Prometheus, Datadog, New Relic, CloudWatch)
• Feature flag platform (LaunchDarkly, Flagsmith, ConfigCat, Unleash)
• Application architecture (monolith, microservices, serverless)
• Deployment frequency and team size