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.