Why ReplicaSets ensure availability in Kubernetes - Why It Works

Introduction

When you run applications in Kubernetes, you want them to keep working even if some parts fail. ReplicaSets help by making sure a set number of copies of your app are always running. If one copy stops, ReplicaSets start a new one automatically.

When you want your app to keep running even if a pod crashes or is deleted.

When you need to run multiple copies of the same app to handle more users.

When you want Kubernetes to automatically fix problems by restarting pods.

When you want to update your app without downtime by managing pods carefully.

When you want to ensure your app is always available during maintenance or failures.

Config File - replicaset.yaml

replicaset.yaml

apiVersion: apps/v1
kind: ReplicaSet
metadata:
  name: example-replicaset
  labels:
    app: my-app
spec:
  replicas: 3
  selector:
    matchLabels:
      app: my-app
  template:
    metadata:
      labels:
        app: my-app
    spec:
      containers:
      - name: my-app-container
        image: nginx:1.23.3
        ports:
        - containerPort: 80

This file defines a ReplicaSet named example-replicaset that keeps 3 copies of the nginx container running.

The replicas field sets how many copies to keep.

The selector tells Kubernetes which pods belong to this ReplicaSet by matching labels.

The template describes the pod to create, including container image and ports.

Commands

This command creates the ReplicaSet in Kubernetes using the configuration file. It tells Kubernetes to start and maintain 3 pods as defined.

Terminal

kubectl apply -f replicaset.yaml

Expected Output

replicaset.apps/example-replicaset created

This command lists all pods with the label app=my-app to verify that 3 pods are running as expected.

Terminal

kubectl get pods -l app=my-app

Expected Output

NAME                             READY   STATUS    RESTARTS   AGE

example-replicaset-abc123        1/1     Running   0          10s

example-replicaset-def456        1/1     Running   0          10s

example-replicaset-ghi789        1/1     Running   0          10s

→

-l - Filter pods by label

This command deletes one of the pods to simulate a failure. ReplicaSet will detect this and create a new pod to keep the count at 3.

Terminal

kubectl delete pod example-replicaset-abc123

Expected Output

pod "example-replicaset-abc123" deleted

Check again to see that the ReplicaSet has started a new pod to replace the deleted one, maintaining availability.

Terminal

kubectl get pods -l app=my-app

Expected Output

NAME                             READY   STATUS    RESTARTS   AGE

example-replicaset-def456        1/1     Running   0          30s

example-replicaset-ghi789        1/1     Running   0          30s

example-replicaset-jkl012        1/1     Running   0          5s

→

-l - Filter pods by label

Key Concept

ReplicaSets keep a set number of pod copies running to ensure your app stays available even if some pods fail or are deleted.

Common Mistakes

Not setting the selector labels correctly in the ReplicaSet spec.

Kubernetes won't know which pods belong to the ReplicaSet, so it won't manage them properly.

Make sure the selector labels exactly match the labels in the pod template.

Deleting pods manually without understanding ReplicaSet behavior.

ReplicaSet will immediately create new pods, which might confuse beginners expecting pods to stay deleted.

Understand that ReplicaSets automatically replace deleted pods to maintain availability.

Summary

Apply a ReplicaSet configuration to tell Kubernetes how many pod copies to keep running.

Use label selectors to link pods to the ReplicaSet for management.

ReplicaSets automatically replace pods if they fail or are deleted to keep your app available.

Practice

1. What is the main purpose of a ReplicaSet in Kubernetes?

easy

A. To manage network traffic between pods

B. To keep a specified number of pod copies running for availability

C. To store data persistently across pods

D. To build container images automatically

Solution

1. Step 1: Understand ReplicaSet's role

   A ReplicaSet ensures that a set number of pod replicas are running at any time.

2. Step 2: Compare options to ReplicaSet function

   Only To keep a specified number of pod copies running for availability describes this function correctly; others describe unrelated features.

3. Final Answer:

   To keep a specified number of pod copies running for availability -> Option B

4. Quick Check:

   ReplicaSet = Pod count management [OK]

Hint: ReplicaSets keep pods alive by counting them [OK]

Common Mistakes:

• Confusing ReplicaSet with persistent storage
• Thinking ReplicaSet manages network traffic
• Assuming ReplicaSet builds container images

2. Which of the following is the correct syntax to create a ReplicaSet with 3 replicas using kubectl?

easy

A. kubectl apply replicaset myapp --replicas=3 --image=myimage

B. kubectl create rs myapp --replicas=3 --image=myimage

C. kubectl run replicaset myapp --replicas=3 --image=myimage

D. kubectl create replicaset myapp --replicas=3 --image=myimage

Solution

1. Step 1: Recall kubectl command for ReplicaSet creation

   The correct command to create a ReplicaSet with replicas and image is 'kubectl run' with appropriate flags.

2. Step 2: Validate each option's syntax

   kubectl run replicaset myapp --replicas=3 --image=myimage is the correct syntax; 'kubectl create rs' is not a valid command, and 'kubectl apply' requires a manifest file.

3. Final Answer:

   kubectl run replicaset myapp --replicas=3 --image=myimage -> Option C

4. Quick Check:

   ReplicaSet creation uses 'kubectl run' with --replicas flag [OK]

Hint: Use 'kubectl run' with --replicas flag [OK]

Common Mistakes:

• Using 'kubectl create rs' which is invalid
• Using full name 'replicaset' which is invalid
• Using 'kubectl apply' without a manifest file

3. Given a ReplicaSet with 2 replicas running, what happens if one pod crashes?

medium

A. The ReplicaSet creates a new pod to maintain 2 replicas

B. The ReplicaSet deletes the remaining pod

C. The ReplicaSet does nothing and leaves 1 pod running

D. The ReplicaSet scales down to 1 replica permanently

Solution

1. Step 1: Understand ReplicaSet behavior on pod failure

   ReplicaSets monitor pods and create new ones if replicas fall below desired count.

2. Step 2: Analyze options based on ReplicaSet function

   Only The ReplicaSet creates a new pod to maintain 2 replicas describes the correct automatic recovery action.

3. Final Answer:

   The ReplicaSet creates a new pod to maintain 2 replicas -> Option A

4. Quick Check:

   ReplicaSet auto-replaces crashed pods [OK]

Hint: ReplicaSets replace crashed pods automatically [OK]

Common Mistakes:

• Thinking ReplicaSet deletes healthy pods
• Assuming ReplicaSet ignores pod crashes
• Believing ReplicaSet reduces replicas on failure

4. You notice your ReplicaSet is not maintaining the desired number of pods. Which of these could be the cause?

medium

A. The ReplicaSet is using the correct image version

B. The ReplicaSet has too many replicas defined

C. The pods are running on nodes with enough resources

D. The ReplicaSet's label selector does not match pod labels

Solution

1. Step 1: Identify how ReplicaSet tracks pods

   ReplicaSets use label selectors to find and manage pods.

2. Step 2: Understand impact of label mismatch

   If selectors don't match pod labels, ReplicaSet cannot manage pods, causing availability issues.

3. Final Answer:

   The ReplicaSet's label selector does not match pod labels -> Option D

4. Quick Check:

   Label selector mismatch breaks ReplicaSet control [OK]

Hint: Check label selectors match pod labels exactly [OK]

Common Mistakes:

• Assuming too many replicas cause pod loss
• Ignoring label selector importance
• Thinking correct image fixes pod count issues

5. How does a ReplicaSet ensure availability during a rolling update of an application?

hard

A. By gradually replacing old pods with new ones while keeping desired replicas

B. By deleting all old pods before creating new pods

C. By scaling down replicas to zero then scaling up again

D. By creating duplicate pods with different labels permanently

Solution

1. Step 1: Understand rolling update process

   Rolling updates replace pods gradually to avoid downtime.

2. Step 2: Analyze ReplicaSet's role in rolling updates

   ReplicaSets maintain desired pod count by creating new pods before deleting old ones.

3. Step 3: Compare options to rolling update behavior

   Only By gradually replacing old pods with new ones while keeping desired replicas correctly describes this gradual replacement ensuring availability.

4. Final Answer:

   By gradually replacing old pods with new ones while keeping desired replicas -> Option A

5. Quick Check:

   Rolling update = gradual pod replacement [OK]

Hint: Rolling updates keep pods up by replacing gradually [OK]

Common Mistakes:

• Deleting all pods at once causing downtime
• Scaling replicas to zero losing availability
• Creating duplicate pods causing conflicts