Implement Canary Deployment Strategy

Scenario

An existing frontend-stable Deployment runs nginx:stable with 10 replicas in the canary namespace and serves custom HTML from the frontend-v1-config ConfigMap.

Implement a canary deployment strategy by creating a new Deployment named frontend-canary using the nginx:alpine image.

Configure the environment to achieve an 80/20 traffic split between the frontend-stable and frontend-canary deployments while maintaining a total of 10 replicas.

Ensure the frontend-service Service continues to target pods labeled app=frontend.

Mount thefrontend-v2-config ConfigMap at /usr/share/nginx/html using subPath: index.html, and add the labels app: frontend and version: v2 to the canary pods.

                     frontend-service
                     (app=frontend)
                           │
            ┌──────────────┴──────────────┐
            │                             │
        80% Traffic                   20% Traffic
            │                             │
     ┌──────▼────────┐           ┌────────▼───────┐
     │frontend-stable│           │ frontend-canary│
     │     80%       │           │     20%        │
     │ nginx:stable  │           │ nginx:alpine   │
     │  version=v1   │           │  version=v2    │
     └───────────────┘           └────────────────┘

curl http://cplane-01:30007   # Test traffic — run multiple times, ~2 in 10 should hit canary

💡Test Cases