Deployment as higher-level abstraction in Kubernetes - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a Kubernetes Deployment?

A Kubernetes Deployment is a higher-level abstraction that manages ReplicaSets and Pods. It helps you declare the desired state of your application, like how many copies should run, and Kubernetes ensures that state is maintained.

beginner

How does a Deployment simplify managing Pods?

Instead of managing individual Pods, a Deployment lets you manage a group of Pods through ReplicaSets. It automatically handles creating, updating, and rolling back Pods to keep your app running smoothly.

intermediate

What happens when you update a Deployment's Pod template?

Kubernetes creates a new ReplicaSet with the updated Pod template and gradually replaces old Pods with new ones. This process is called a rolling update and helps avoid downtime.

intermediate

Why use Deployments instead of directly managing ReplicaSets?

Deployments provide easier updates, rollbacks, and scaling. They automate complex tasks like rolling updates and ensure your app stays available without manual intervention.

beginner

What is the role of ReplicaSets in a Deployment?

ReplicaSets ensure that a specified number of Pod replicas are running at any time. Deployments create and manage ReplicaSets to maintain the desired state of your application.

What does a Kubernetes Deployment primarily manage?

A ReplicaSets and Pods

B Nodes and Clusters

C Services and Ingress

D Persistent Volumes

Deployments manage ReplicaSets and Pods to maintain the desired state of your application.

What is the main benefit of using a Deployment for updates?

A Deleting all Pods at once

B Manual Pod replacement

C Rolling updates without downtime

D Ignoring Pod failures

Deployments perform rolling updates that replace Pods gradually to avoid downtime.

If you want to roll back to a previous version of your app, what Kubernetes object helps you do this easily?

A Pod

B ConfigMap

C Service

D Deployment

Deployments keep track of revisions and allow easy rollbacks to previous versions.

Which Kubernetes object ensures the number of Pod replicas is maintained?

A ReplicaSet

B Deployment

C Namespace

D Ingress

ReplicaSets maintain the desired number of Pod replicas running.

What happens if a Pod managed by a Deployment crashes?

A Deployment ignores it

B ReplicaSet creates a new Pod to replace it

C Node is deleted

D Service stops

The ReplicaSet automatically creates a new Pod to keep the desired number of replicas.

Explain how a Kubernetes Deployment manages application updates and maintains availability.

Think about how Deployments handle changes to your app without stopping it.

Describe the relationship between Deployments, ReplicaSets, and Pods in Kubernetes.

Consider the hierarchy and roles of each object.

Practice

1. What is the main purpose of a Kubernetes Deployment?

easy

A. To provide network access to pods

B. To store data persistently across pods

C. To schedule pods on specific nodes manually

D. To manage multiple copies of an application and keep them running

Solution

1. Step 1: Understand Deployment role

   A Deployment manages the desired number of pod replicas and ensures they stay running.

2. Step 2: Compare other options

   Options A, B, and D describe Services, Persistent Volumes, and manual scheduling, which are not Deployment's main purpose.

3. Final Answer:

   To manage multiple copies of an application and keep them running -> Option D

4. Quick Check:

   Deployment manages pods = C [OK]

Hint: Deployment controls app copies and uptime [OK]

Common Mistakes:

• Confusing Deployment with Service or Volume
• Thinking Deployment schedules pods manually
• Assuming Deployment stores data

2. Which of the following is the correct minimal YAML snippet to define a Deployment selector matching pods with label app: myapp?

easy

A. selector:
matchLabels:
app: myapp

B. selector:
labels:
app: myapp

C. selector:
matchLabels:
name: myapp

D. selector:
matchExpressions:
- key: app
operator: In
values: [myapp]

Solution

1. Step 1: Recall Deployment selector syntax

   The selector must use matchLabels with key-value pairs matching pod labels.

2. Step 2: Check options

   selector: matchLabels: app: myapp uses correct matchLabels with app: myapp. selector: labels: app: myapp uses wrong key labels. selector: matchLabels: name: myapp uses wrong label key name. selector: matchExpressions: - key: app operator: In values: [myapp] uses matchExpressions which is valid but more complex and not minimal.

3. Final Answer:

   selector: matchLabels: app: myapp -> Option A

4. Quick Check:

   Use matchLabels with correct key = A [OK]

Hint: Use matchLabels with exact pod label keys [OK]

Common Mistakes:

• Using 'labels' instead of 'matchLabels'
• Mismatching label keys in selector
• Confusing matchLabels with matchExpressions

3. Given this Deployment YAML snippet, what will be the number of pods running after applying it?

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

medium

A. 0 pods running due to label mismatch

B. 1 pod running

C. 3 pods running

D. Deployment will fail to create pods

Solution

1. Step 1: Check replicas and labels

   The Deployment requests 3 replicas and the selector matches pods with label app: test. The pod template labels match this exactly.

2. Step 2: Confirm pod creation

   Since labels match, Kubernetes will create 3 pods as requested.

3. Final Answer:

   3 pods running -> Option C

4. Quick Check:

   Matching labels + replicas 3 = 3 pods [OK]

Hint: Match selector and template labels to get pods [OK]

Common Mistakes:

• Assuming label mismatch causes zero pods
• Thinking Deployment fails without errors
• Ignoring replicas count

4. You applied a Deployment YAML but no pods are created. Which issue is most likely causing this?

medium

A. The Deployment metadata name is missing

B. The Deployment selector labels do not match the pod template labels

C. The replicas field is set to zero

D. The container image name is missing

Solution

1. Step 1: Understand Deployment selector importance

   The Deployment uses the selector to find pods it manages. If selector labels don't match pod template labels, no pods are created.

2. Step 2: Evaluate other options

   Missing image name causes pod creation failure but usually with errors. Replicas zero means no pods but is explicit. Missing metadata name causes YAML validation error.

3. Final Answer:

   The Deployment selector labels do not match the pod template labels -> Option B

4. Quick Check:

   Selector-template label mismatch = no pods [OK]

Hint: Check selector and template labels match exactly [OK]

Common Mistakes:

• Ignoring label mismatch
• Assuming missing image silently creates no pods
• Confusing replicas zero with label mismatch

5. You want to update your app smoothly without downtime using a Deployment. Which feature of Deployment helps achieve this?

hard

A. Rolling update strategy that replaces pods gradually

B. Manual pod deletion to force restart

C. Setting replicas to zero before update

D. Using a StatefulSet instead of Deployment

Solution

1. Step 1: Identify update strategies in Deployment

   Deployment supports rolling updates that replace pods one by one, keeping the app available.

2. Step 2: Compare other options

   Manual deletion causes downtime. Setting replicas to zero stops all pods. StatefulSet is for stateful apps, not smooth rolling updates.

3. Final Answer:

   Rolling update strategy that replaces pods gradually -> Option A

4. Quick Check:

   Rolling update = smooth app update [OK]

Hint: Rolling update replaces pods one by one [OK]

Common Mistakes:

• Deleting pods manually causes downtime
• Scaling replicas to zero stops app
• Confusing StatefulSet with Deployment update