Creating Deployments with YAML in Kubernetes - Performance & Efficiency

Time Complexity: Creating Deployments with YAML

O(n)

Understanding Time Complexity

When creating deployments with YAML in Kubernetes, it's important to understand how the time to apply these configurations grows as the deployment size increases.

We want to know how the system handles more replicas or containers and how that affects the work Kubernetes does.

Scenario Under Consideration

Analyze the time complexity of the following Kubernetes deployment YAML snippet.

apiVersion: apps/v1
kind: Deployment
metadata:
  name: example-deployment
spec:
  replicas: 3
  selector:
    matchLabels:
      app: example
  template:
    metadata:
      labels:
        app: example
    spec:
      containers:
      - name: example-container
        image: nginx:latest

This YAML defines a deployment that creates 3 replicas of an nginx container.

Identify Repeating Operations

• Primary operation: Kubernetes creates and manages each pod replica defined in the deployment.
• How many times: The creation and management steps repeat once for each replica specified (here, 3 times).

How Execution Grows With Input

As the number of replicas increases, Kubernetes performs more work to create and manage each pod.

Input Size (replicas)	Approx. Operations
10	10 pod creations and management steps
100	100 pod creations and management steps
1000	1000 pod creations and management steps

Pattern observation: The work grows directly with the number of replicas; doubling replicas roughly doubles the work.

Final Time Complexity

Time Complexity: O(n)

This means the time to create and manage pods grows linearly with the number of replicas.

Common Mistake

[X] Wrong: "Creating more replicas happens instantly and does not add extra work."

[OK] Correct: Each replica requires Kubernetes to create and monitor a pod, so more replicas mean more work and time.

Interview Connect

Understanding how deployment size affects Kubernetes operations helps you explain system behavior clearly and shows you grasp resource management basics.

Self-Check

"What if we added multiple containers inside each pod template? How would the time complexity change?"

Practice

1. What is the main purpose of a Deployment in Kubernetes when defined using a YAML file?

easy

A. To manage and update multiple copies of an application smoothly

B. To store data persistently across pods

C. To expose an application to the internet

D. To define network policies between pods

Solution

1. Step 1: Understand Deployment role

   A Deployment manages the lifecycle of pods, ensuring the desired number of replicas run and updates happen smoothly.

2. Step 2: Compare options

   Options B, C, and D describe other Kubernetes resources (PersistentVolume, Service, NetworkPolicy), not Deployment.

3. Final Answer:

   To manage and update multiple copies of an application smoothly -> Option A

4. Quick Check:

   Deployment = Manage app replicas and updates [OK]

Hint: Deployments control app copies and updates, not storage or networking [OK]

Common Mistakes:

• Confusing Deployment with Service or PersistentVolume
• Thinking Deployment exposes apps externally
• Assuming Deployment manages network policies

2. Which of the following YAML snippets correctly sets the number of pod replicas to 3 in a Deployment?

easy

A. replicas: 3

B. replicaCount: 3

C. count: 3

D. podReplicas: 3

Solution

1. Step 1: Identify correct replicas field

   The correct field to specify pod count in Deployment YAML is replicas.

2. Step 2: Check other options

   Fields like replicaCount, count, or podReplicas are invalid and will cause errors.

3. Final Answer:

   replicas: 3 -> Option A

4. Quick Check:

   Use 'replicas' to set pod count [OK]

Hint: Use 'replicas' exactly to set pod count in Deployment YAML [OK]

Common Mistakes:

• Using incorrect field names like replicaCount
• Misspelling 'replicas' or using camelCase
• Placing replicas under wrong YAML level

3. Given this Deployment YAML snippet, what will be the label selector used to match pods?

selector:
  matchLabels:
    app: myapp
    tier: frontend

medium

A. Pods with any label app or tier

B. Pods with label app=myapp only

C. Pods with label tier=frontend only

D. Pods with labels app=myapp and tier=frontend

Solution

1. Step 1: Understand matchLabels selector

   The matchLabels requires all listed labels to match exactly for pod selection.

2. Step 2: Analyze given labels

   Both app: myapp and tier: frontend must be present on pods to match.

3. Final Answer:

   Pods with labels app=myapp and tier=frontend -> Option D

4. Quick Check:

   matchLabels means all labels must match [OK]

Hint: matchLabels requires all labels to match exactly [OK]

Common Mistakes:

• Assuming matchLabels matches any one label
• Confusing matchLabels with matchExpressions
• Ignoring one of the labels in selector

4. You wrote this Deployment YAML but your pods are not created. What is the error?

apiVersion: apps/v1
kind: Deployment
metadata:
  name: webapp
spec:
  replicas: 2
  selector:
    matchLabels:
      app: webapp
  template:
    metadata:
      labels:
        app: frontend
    spec:
      containers:
      - name: webapp
        image: nginx

medium

A. No container ports defined

B. Incorrect apiVersion for Deployment

C. Selector labels do not match template labels

D. Missing container image tag

Solution

1. Step 1: Check selector and template labels

   The selector matchLabels: app: webapp does not match template labels: app: frontend. Labels must match exactly or Deployment creation fails.

2. Step 2: Verify other fields

   Ports are optional for pod creation; apiVersion is correct; image tag defaults to latest.

3. Final Answer:

   Selector labels do not match template labels -> Option C

4. Quick Check:

   Selector must match template labels [OK]

Hint: Selector labels must exactly match template labels [OK]

Common Mistakes:

• Assuming container ports are required for pod creation
• Thinking image tag is mandatory
• Confusing apiVersion for Deployment

5. You want to update your Deployment to run 5 replicas and change the container image to 'nginx:1.21'. Which YAML snippet correctly applies both changes?

hard

A. spec:
replicas: 5
template:
spec:
containers:
- name: nginx
image: nginx:1.21

B. spec:
replicas: 5
template:
metadata:
labels:
app: nginx
spec:
containers:
- name: nginx
image: nginx:1.21

C. spec:
replicas: 5
containers:
- name: nginx
image: nginx:1.21

D. spec:
template:
spec:
containers:
- name: nginx
image: nginx:1.21
replicas: 5

Solution

1. Step 1: Understand Deployment spec structure

   The replicas field is directly under spec. The pod template is under spec.template, which must include metadata.labels and spec.containers.

2. Step 2: Check each option's correctness

   spec:
     replicas: 5
     template:
       spec:
         containers:
         - name: nginx
           image: nginx:1.21

   misses metadata.labels under template, which is required for selector matching.

   spec:
     replicas: 5
     containers:
     - name: nginx
       image: nginx:1.21

   places containers directly under spec, which is invalid.

   spec:
     template:
       spec:
         containers:
         - name: nginx
           image: nginx:1.21
     replicas: 5

   places replicas after template, which is allowed but missing labels in template metadata.

   spec:
     replicas: 5
     template:
       metadata:
         labels:
           app: nginx
       spec:
         containers:
         - name: nginx
           image: nginx:1.21

   correctly includes replicas, template metadata labels, and container spec with updated image.

3. Final Answer:

   spec: replicas: 5, template with metadata.labels app: nginx, containers image: nginx:1.21 -> Option B

4. Quick Check:

   replicas under spec, labels in template metadata, containers in template spec [OK]

Hint: Always include labels in template metadata for selector matching [OK]

Common Mistakes:

• Omitting labels in pod template metadata
• Placing containers outside template spec
• Misplacing replicas field