Pods and deployments for services in Microservices - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a Pod in Kubernetes?

A Pod is the smallest deployable unit in Kubernetes. It represents one or more containers that share storage, network, and a specification for how to run the containers.

beginner

What is the purpose of a Deployment in Kubernetes?

A Deployment manages Pods and ReplicaSets. It ensures the desired number of Pods are running, handles updates, and can roll back changes if needed.

intermediate

How do Deployments help with scaling services?

Deployments allow you to easily increase or decrease the number of Pod replicas, enabling your service to handle more or less traffic as needed.

intermediate

Why should containers in a Pod share the same network namespace?

Sharing the network namespace allows containers in a Pod to communicate with each other using localhost, making coordination simpler and faster.

beginner

What happens if a Pod crashes in a Deployment?

The Deployment controller detects the crash and automatically creates a new Pod to replace the failed one, keeping the service running smoothly.

What is the smallest deployable unit in Kubernetes?

A Node

B Deployment

C Service

D Pod

A Pod is the smallest deployable unit that can contain one or more containers.

Which Kubernetes object manages rolling updates for Pods?

A ConfigMap

B Service

C Deployment

D Namespace

Deployments handle rolling updates and rollbacks for Pods.

How do containers inside the same Pod communicate?

A Through separate IP addresses

B Using localhost network

C Via external service

D They cannot communicate

Containers in the same Pod share the network namespace and communicate via localhost.

What ensures the desired number of Pod replicas are running?

A Deployment

B ReplicaSet

C Pod

D Ingress

Deployments manage ReplicaSets to maintain the desired number of Pods.

If a Pod crashes, what does the Deployment do?

A Creates a new Pod to replace it

B Deletes the Deployment

C Does nothing

D Scales down the service

The Deployment controller replaces crashed Pods automatically.

Explain how Pods and Deployments work together to keep a microservice running smoothly.

Think about how Kubernetes keeps your app available and updated.

Describe the benefits of using Deployments for scaling microservices.

Consider how you handle more users or traffic.

Practice

1. What is the main role of a Pod in a microservices architecture?

easy

A. To manage updates and scaling of containers

B. To run one or more containers together as a single unit

C. To route network traffic between services

D. To store persistent data for containers

Solution

1. Step 1: Understand what a Pod is

   A Pod is the smallest deployable unit in Kubernetes that runs one or more containers together.

2. Step 2: Differentiate Pod from other components

   Deployments manage Pods, Services route traffic, and persistent storage is handled separately.

3. Final Answer:

   To run one or more containers together as a single unit -> Option B

4. Quick Check:

   Pod = container unit [OK]

Hint: Pods run containers; deployments manage pods [OK]

Common Mistakes:

• Confusing Pods with Deployments
• Thinking Pods handle networking
• Assuming Pods store data

2. Which of the following is the correct YAML snippet to define a Deployment that runs 3 replicas of a Pod?

easy

A. kind: Pod\nreplicas: 3\nmetadata:\n name: my-pod

B. replicas: 3\nkind: Service\nmetadata:\n name: my-service

C. replicas: 3\nkind: Deployment\nmetadata:\n name: my-deployment

D. kind: Deployment\nmetadata:\n name: my-deployment\nreplicas: three

Solution

1. Step 1: Identify correct kind and replicas field

   Deployment kind is correct and replicas should be a number, here 3.

2. Step 2: Check metadata and syntax

   Metadata name is valid; 'replicas: three' is invalid because replicas must be numeric.

3. Final Answer:

   replicas: 3\nkind: Deployment\nmetadata:\n name: my-deployment -> Option C

4. Quick Check:

   Deployment with numeric replicas = correct YAML [OK]

Hint: Deployments use 'kind: Deployment' and numeric replicas [OK]

Common Mistakes:

• Using 'kind: Pod' instead of Deployment
• Setting replicas as a word instead of number
• Confusing Service with Deployment

3. Given this Deployment YAML snippet, how many Pods will be running after applying it?

apiVersion: apps/v1
kind: Deployment
metadata:
  name: web-app
spec:
  replicas: 4
  selector:
    matchLabels:
      app: web
  template:
    metadata:
      labels:
        app: web
    spec:
      containers:
      - name: web-container
        image: nginx

medium

A. 4 Pods

B. 0 Pods until manually started

C. 1 Pod

D. Depends on the number of nodes

Solution

1. Step 1: Read replicas count in Deployment spec

   The replicas field is set to 4, meaning Kubernetes will maintain 4 Pods.

2. Step 2: Understand Deployment behavior

   Deployment automatically creates and manages the specified number of Pods.

3. Final Answer:

   4 Pods -> Option A

4. Quick Check:

   replicas = 4 Pods running [OK]

Hint: replicas number = Pods count after deployment [OK]

Common Mistakes:

• Assuming only 1 Pod runs by default
• Thinking Pods need manual start
• Confusing nodes with Pod count

4. You applied a Deployment YAML but notice no Pods are running. Which is the most likely cause?
apiVersion: apps/v1 kind: Deployment metadata: name: api-server spec: replicas: 3 selector: matchLabels: app: api template: metadata: labels: app: backend spec: containers: - name: api-container image: myapi:latest

medium

A. The Deployment kind is incorrect

B. The replicas count is too high for the cluster

C. The container image name is invalid

D. The selector labels do not match the Pod template labels

Solution

1. Step 1: Compare selector and template labels

   The selector uses label 'app: api' but the Pod template labels 'app: backend' which do not match.

2. Step 2: Understand label matching importance

   Deployment uses selector to manage Pods; mismatch means no Pods are controlled or created.

3. Final Answer:

   The selector labels do not match the Pod template labels -> Option D

4. Quick Check:

   Selector labels must match Pod labels [OK]

Hint: Selector and Pod labels must match exactly [OK]

Common Mistakes:

• Ignoring label mismatch
• Assuming image name causes no Pods
• Thinking replicas count blocks Pod creation

5. You want to update a microservice with zero downtime using Kubernetes. Which approach best uses Pods and Deployments to achieve this?

hard

A. Update the Deployment with a new image version; Kubernetes creates new Pods and gradually replaces old ones

B. Delete all old Pods manually and then create new Pods with the updated image

C. Scale down the Deployment to zero replicas, then scale up with the new image

D. Create a new Deployment with the updated image and delete the old Deployment immediately

Solution

1. Step 1: Understand Deployment update strategy

   Deployments support rolling updates that create new Pods and remove old Pods gradually.

2. Step 2: Compare options for zero downtime

   Manual deletion or scaling down causes downtime; creating new Deployment causes conflicts.

3. Final Answer:

   Update the Deployment with a new image version; Kubernetes creates new Pods and gradually replaces old ones -> Option A

4. Quick Check:

   Rolling update = zero downtime update [OK]

Hint: Use Deployment rolling updates for zero downtime [OK]

Common Mistakes:

• Deleting Pods manually causing downtime
• Scaling to zero causes service interruption
• Creating new Deployment causes conflicts