ci-cd-advanced

Use Argo Rollouts to define canary steps that shift traffic gradually, such as 10% then 50% then 100%, with pauses between steps. Attach an AnalysisTemplate that queries Prometheus for error rates and automatically rolls back if thresholds are breached.

Blue-green runs two full environments and switches all traffic instantly after smoke tests pass, keeping the old version for immediate rollback. Canary shifts traffic gradually to the new version, limiting blast radius to a small user percentage while monitoring metrics.

After deploying, run a smoke test against the health endpoint and query Prometheus for error rates over several minutes. If checks fail, execute kubectl rollout undo on the deployment to restore the previous version automatically.

Yes, Argo Rollouts supports Istio through the trafficRouting configuration that references a VirtualService. It adjusts traffic weights between stable and canary versions as rollout steps progress.

Feature flags decouple code deployment from feature release, letting you enable functionality for specific users or percentages without redeploying. Use them when you need user-level targeting or want to ship code dark and enable it independently of infrastructure rollouts.

Track deployment frequency, lead time for changes, change failure rate, and mean time to recovery. Instrument pipelines with Prometheus counters and histograms for deployment totals, durations, and statuses to compute these metrics.