Why ReplicaSets ensure availability in Kubernetes - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

How does a ReplicaSet maintain pod availability?

In Kubernetes, a ReplicaSet is used to keep a stable set of replica pods running. Which of the following best explains how a ReplicaSet ensures availability?

A It continuously monitors the number of pods and creates new pods if some are deleted or fail.

B It schedules pods only once and does not react to pod failures.

C It manually restarts pods when a user triggers a command.

D It stores pod data to recover pods after a node failure.

💡 Hint

Think about what happens if a pod crashes or is deleted.

A ReplicaSet constantly watches the pods it manages. If any pod stops running or is deleted, it creates a new one to keep the desired number of replicas. This automatic replacement keeps the application available.

💻 Command Output

intermediate

Output of checking ReplicaSet pod count

You run the command kubectl get rs myapp-replicaset and see the following output:

NAME               DESIRED   CURRENT   READY   AGE
myapp-replicaset   3         2         2       10m

What does this output indicate about the ReplicaSet's availability?

A The ReplicaSet is paused and not managing pods.

B All desired pods are running and ready, so availability is perfect.

C The ReplicaSet wants 3 pods but currently only 2 are running and ready, so availability is reduced.

D The ReplicaSet has more pods than desired, which may cause resource waste.

💡 Hint

Look at the numbers under DESIRED, CURRENT, and READY.

The ReplicaSet wants 3 pods (DESIRED), but only 2 are currently running (CURRENT) and ready (READY). This means one pod is missing or not ready, so availability is not at full capacity.

🔀 Workflow

advanced

Steps ReplicaSet takes when a pod fails

When a pod managed by a ReplicaSet crashes, what is the correct sequence of actions the ReplicaSet controller performs to maintain availability?

A 1,2,3,4

B 2,1,3,4

C 1,3,2,4

D 3,1,2,4

💡 Hint

Think about detection first, then status update, then creation, then readiness.

The ReplicaSet first detects the pod failure, updates its status, creates a replacement pod, and waits for it to become ready to maintain availability.

❓ Troubleshoot

advanced

Why is a ReplicaSet not creating new pods?

You notice your ReplicaSet is set to 4 replicas, but only 2 pods are running. The ReplicaSet is not creating new pods. Which of the following is the most likely cause?

A The ReplicaSet controller is paused and not managing pods.

B The cluster has insufficient resources to schedule new pods.

C The pods are stuck in the Terminating state and blocking new pods.

D The ReplicaSet spec has a syntax error preventing pod creation.

💡 Hint

Consider what happens if the cluster cannot find space for new pods.

If the cluster lacks CPU or memory resources, the scheduler cannot place new pods, so the ReplicaSet cannot create them even if desired.

✅ Best Practice

expert

Ensuring high availability with ReplicaSets across nodes

To maximize availability, how should you configure ReplicaSets in a Kubernetes cluster with multiple nodes?

A Configure the ReplicaSet to schedule all pods on the same node for easier management.

B Set the ReplicaSet to a single replica to avoid resource conflicts.

C Use a ReplicaSet with no replicas and manually create pods on each node.

D Set the ReplicaSet to have multiple replicas and use pod anti-affinity rules to spread pods across different nodes.

💡 Hint

Think about spreading pods to avoid single points of failure.

Using multiple replicas with pod anti-affinity spreads pods across nodes, so if one node fails, others keep running pods, ensuring high availability.