Why Kubernetes manages microservice deployment in Microservices - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why does Kubernetes use pods for microservice deployment?

Kubernetes groups containers into pods. What is the main reason for this design when deploying microservices?

A Pods replace the need for container images in Kubernetes.

B Pods are used to store persistent data for microservices.

C Pods automatically scale the number of microservices without configuration.

D Pods allow multiple containers to share resources and communicate easily within the same deployment unit.

💡 Hint

Think about how containers inside a pod interact and share resources.

Kubernetes pods group containers that need to work closely together. They share storage, network, and specifications, making communication and resource sharing simple.

💻 Command Output

intermediate

What is the output of 'kubectl get pods' after deploying a microservice?

After deploying a microservice with Kubernetes, you run kubectl get pods. What output do you expect to see?

Microservices

kubectl get pods

A

PODS           READY   STATUS
myservice      1/1     Completed

B

NAME           READY   STATUS    RESTARTS   AGE
myservice-abc   1/1     Running   0          5m

C

NAME           STATUS    IMAGE
myservice      Running   nginx

D No resources found.

💡 Hint

Look for the standard columns shown by kubectl get pods.

The command kubectl get pods lists pods with columns like NAME, READY, STATUS, RESTARTS, and AGE. Option B matches this format and shows a running pod.

🔀 Workflow

advanced

Order the steps to deploy a microservice on Kubernetes

Arrange the steps in the correct order to deploy a microservice using Kubernetes.

A 1,2,3,4

B 2,1,4,3

C 1,3,2,4

D 3,1,2,4

💡 Hint

Think about writing configuration first, then applying it, checking status, and finally exposing the service.

The correct workflow is to write the deployment YAML, apply it, verify pods are running, then expose the deployment with a service.

❓ Troubleshoot

advanced

Why does a Kubernetes pod stay in 'CrashLoopBackOff' status?

You deployed a microservice pod, but it stays in CrashLoopBackOff status. What is the most likely cause?

A The pod has completed its task and is shutting down normally.

B The pod is waiting for a network connection to be established.

C The container inside the pod is repeatedly failing to start due to an error.

D The pod is successfully running but not responding to requests.

💡 Hint

Think about what 'CrashLoopBackOff' means in Kubernetes pod status.

'CrashLoopBackOff' means the container inside the pod keeps crashing and Kubernetes is trying to restart it repeatedly.

✅ Best Practice

expert

What is the best practice for managing microservice updates in Kubernetes?

When updating a microservice deployed on Kubernetes, what is the recommended approach to avoid downtime?

A Use rolling updates to gradually replace old pods with new ones without stopping the service.

B Delete all existing pods and then create new pods with the updated version immediately.

C Update the container image on the existing pods without restarting them.

D Stop the Kubernetes cluster, update the microservice, then restart the cluster.

💡 Hint

Consider how Kubernetes handles updates to keep services available.

Rolling updates allow Kubernetes to replace pods one by one, ensuring the service stays available during updates.

Practice

1. Why does Kubernetes manage microservice deployment instead of manually running each service?

easy

A. Because it replaces the need for any servers

B. Because it automates starting, stopping, and scaling services reliably

C. Because it writes the code for microservices automatically

D. Because it only works with one service at a time

Solution

1. Step 1: Understand manual deployment challenges

   Manually running many microservices is hard to keep track of and scale.

2. Step 2: Role of Kubernetes in deployment

   Kubernetes automates managing service lifecycles, scaling, and recovery to keep apps running smoothly.

3. Final Answer:

   Because it automates starting, stopping, and scaling services reliably -> Option B

4. Quick Check:

   Automation of service management = B [OK]

Hint: Kubernetes automates service control, not replaces servers or code [OK]

Common Mistakes:

• Thinking Kubernetes replaces servers
• Believing Kubernetes writes app code
• Assuming Kubernetes handles only one service

2. Which of the following is the correct Kubernetes command to deploy a microservice from a YAML file named service.yaml?

easy

A. kubectl apply -f service.yaml

B. kubectl run service.yaml

C. kubectl start service.yaml

D. kubectl create service.yaml

Solution

1. Step 1: Identify the command to apply configuration files

   The kubectl apply -f command applies changes from a YAML file to the cluster.

2. Step 2: Check other options for correctness

   kubectl run is for running pods directly, kubectl start and kubectl create do not accept YAML files directly.

3. Final Answer:

   kubectl apply -f service.yaml -> Option A

4. Quick Check:

   Apply YAML file = kubectl apply -f [OK]

Hint: Use 'kubectl apply -f' to deploy YAML files [OK]

Common Mistakes:

• Using 'kubectl run' to deploy YAML files
• Trying 'kubectl start' which is invalid
• Confusing 'kubectl create' with applying configs

3. Given this Kubernetes YAML snippet for a microservice pod:

apiVersion: v1
kind: Pod
metadata:
  name: myservice
spec:
  containers:
  - name: app
    image: myapp:v1
    ports:
    - containerPort: 80

What will happen if the pod crashes unexpectedly?

medium

A. The pod will restart only if the image is updated

B. The pod will stay crashed until manually restarted

C. Kubernetes will automatically restart the pod to keep the service running

D. Kubernetes will delete the pod and not recreate it

Solution

1. Step 1: Understand pod restart policy default

   By default, Kubernetes restarts pods automatically if they crash to maintain service availability.

2. Step 2: Check other options for correctness

   Pods do not stay crashed without restart, nor are they deleted permanently without recreation, and restarts are not tied to image updates.

3. Final Answer:

   Kubernetes will automatically restart the pod to keep the service running -> Option C

4. Quick Check:

   Pod auto-restart on crash = D [OK]

Hint: Pods auto-restart by default to keep services alive [OK]

Common Mistakes:

• Thinking pods stay crashed until manual restart
• Believing pods delete permanently on crash
• Assuming restart depends on image updates

4. You deployed a microservice with Kubernetes, but it keeps crashing. The YAML file has this snippet:

spec:
  containers:
  - name: app
    image: myapp:v1
    ports:
    - containerPort: 80
  restartPolicy: Never

What is the problem and how to fix it?

medium

A. The pod name is missing; add metadata name

B. The containerPort is wrong; change it to 8080

C. The image version is invalid; update to 'v2'

D. The restartPolicy 'Never' stops restarts; change it to 'Always' to fix

Solution

1. Step 1: Identify restartPolicy effect

   Setting restartPolicy: Never means Kubernetes will not restart the pod if it crashes.

2. Step 2: Fix by changing restartPolicy

   Changing restartPolicy to Always lets Kubernetes restart the pod automatically to keep it running.

3. Final Answer:

   The restartPolicy 'Never' stops restarts; change it to 'Always' to fix -> Option D

4. Quick Check:

   restartPolicy 'Always' enables auto-restart [OK]

Hint: Use restartPolicy 'Always' to auto-restart pods [OK]

Common Mistakes:

• Changing port without checking crash cause
• Updating image version without error info
• Ignoring restartPolicy effect

5. You want to deploy a microservice that must always be available, even if some pods fail. Which Kubernetes feature helps achieve this and how?

hard

A. Use a Deployment with replicas to run multiple pod copies for high availability

B. Use a single Pod with restartPolicy set to Never

C. Use a ConfigMap to store pod data for recovery

D. Use a ServiceAccount to control pod permissions

Solution

1. Step 1: Understand high availability needs

   Running multiple copies of a microservice ensures it stays available if some pods fail.

2. Step 2: Use Kubernetes Deployment with replicas

   A Deployment manages multiple pod replicas and automatically replaces failed pods to maintain availability.

3. Final Answer:

   Use a Deployment with replicas to run multiple pod copies for high availability -> Option A

4. Quick Check:

   Deployment + replicas = high availability [OK]

Hint: Deploy replicas with Deployment for service uptime [OK]

Common Mistakes:

• Using single pod with no replicas
• Confusing ConfigMap with availability
• Mixing permissions with availability