Canary

CKAD v1.35 · Application Deployment (20%) → "Use Kubernetes primitives to implement common deployment strategies (e.g. blue/green or canary)" Target time: 10 minutes

Namespace rollout runs Deployment web-stable (image reply "v1") with 5 replicas, fronted by Service web on port 80.

Implement a CANARY release using only core Kubernetes primitives — no service mesh, no ingress weights:

1. Add a Deployment web-canary running the "v2" image, sized so that roughly 20% of requests reach it.
2. Service web must load-balance across BOTH deployments.
3. Every pod must still be individually addressable by its track: stable pods labelled track=stable, canary pods track=canary.
4. Do not change the total pod count from 5.

Verify with ~50 requests that roughly 1 in 5 returns v2.