Design a Canary Deployment Strategy for Corso Nove Checkout
Overview
What this challenge is about.
Design canary rollout steps and rollback rules for Corso Nove Checkout services using SLO metrics. Complete the challenge to earn a verifiable certificate.
The scenario
Corso Nove is a premium streetwear label running a direct-to-consumer online store out of Milan, where evening and weekend traffic spikes drive most checkout volume. Its backend runs on a self-managed Kubernetes cluster with an Istio service mesh and Prometheus monitoring, but releases today go straight to all users with no gradual rollout or automated safety net.
The Brief
What you'll do, and what you'll demonstrate.
Corso Nove needs a progressive-delivery design that gradually rolls out backend releases and automatically rolls them back on a metric breach, so a bad deploy can no longer take down checkout.
Earning criteria — what you'll demonstrate
- Translate a real incident postmortem into measurable reliability targets and rollback conditions.
- Design canary analysis metrics that combine technical signals (success rate, tail latency) with a business signal (orders per minute).
- Reason about canary step weights, step intervals, and time-to-rollback math against a service-level objective window.
- Compare Flagger and Argo Rollouts and justify a controller choice for an existing Kubernetes plus Istio plus Prometheus stack.
- Communicate an operational design clearly enough that a senior reliability engineer will trust and approve it.
Program Fit
Where this fits in your program.
Sharpens the same skills your degree expects you to demonstrate.
Aligned coursework coming soon.
Skills
Skills you'll demonstrate.
Each one shows up on your verified credential.
- Flagger
Apply flagger to solve real industry problems and demonstrate production-level capability.
- Argo Rollouts
Apply argo rollouts to solve real industry problems and demonstrate production-level capability.
- Canary Deployment
Apply canary deployment to solve real industry problems and demonstrate production-level capability.
- Istio
Apply istio to solve real industry problems and demonstrate production-level capability.
- Prometheus
Apply prometheus to solve real industry problems and demonstrate production-level capability.
- Progressive Delivery
Apply progressive delivery to solve real industry problems and demonstrate production-level capability.
Careers
Career paths this challenge builds toward
Completing this challenge demonstrates skills that transfer directly to these roles:
Site Reliability Engineer
Designing metric-driven canary rollouts and automated rollback policy is core reliability work; this challenge has you turn an incident into a release-safety design on a real Kubernetes and Istio stack, exactly the deliverable a reliability team owns and defends.
This challenge sharpens
- progressive-delivery
- canary-deployment
- prometheus
Platform Engineer
Platform engineers build the deployment guardrails other teams ship through. Choosing and configuring a rollout controller on top of a service mesh, and justifying the trade-offs, maps directly to designing safe self-service release infrastructure.
This challenge sharpens
- flagger
- argo-rollouts
- istio
DevOps Engineer
This challenge bridges to DevOps work by connecting release automation, observability, and rollback logic into one safe delivery pipeline, the kind of progressive-delivery practice DevOps engineers introduce to cut deployment risk.
This challenge sharpens
- progressive-delivery
- canary-deployment
- flagger