Canary deployments in Kubernetes - Time & Space Complexity

Time Complexity: Canary deployments

O(n)

Understanding Time Complexity

When using canary deployments in Kubernetes, it's important to understand how the deployment process scales as you increase the number of users or pods.

We want to know how the time to roll out changes as the system grows.

Scenario Under Consideration

Analyze the time complexity of the following Kubernetes deployment snippet for a canary release.

apiVersion: apps/v1
kind: Deployment
metadata:
  name: my-app-canary
spec:
  replicas: 10
  selector:
    matchLabels:
      app: my-app-canary
  template:
    metadata:
      labels:
        app: my-app-canary
    spec:
      containers:
      - name: my-app-container
        image: my-app:v2-canary
        resources:
          limits:
            cpu: "500m"
            memory: "256Mi"

This snippet creates 10 pods running the canary version of the app alongside existing stable pods.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Creating and updating each pod in the canary deployment.
• How many times: Once per replica, here 10 times for 10 pods.

How Execution Grows With Input

As the number of replicas (pods) increases, the deployment controller performs operations for each pod.

Input Size (n)	Approx. Operations
10	10 pod creations and updates
100	100 pod creations and updates
1000	1000 pod creations and updates

Pattern observation: The work grows directly with the number of pods you deploy.

Final Time Complexity

Time Complexity: O(n)

This means the time to complete the canary deployment grows linearly with the number of pods you create.

Common Mistake

[X] Wrong: "Deploying more pods in a canary release takes the same time no matter how many pods there are."

[OK] Correct: Each pod requires separate creation and readiness checks, so more pods mean more work and longer deployment time.

Interview Connect

Understanding how deployment time scales helps you design better release strategies and shows you can think about system growth clearly.

Self-Check

"What if we used a rolling update strategy that updates pods in batches instead of all at once? How would the time complexity change?"