Why ReplicaSets ensure availability in Kubernetes - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to specify the number of pod replicas in a ReplicaSet.

Kubernetes

replicas: [1]

Drag options to blanks, or click blank then click option'

A5

B3

C1

D0

Attempts:

3 left

💡 Hint

Common Mistakes

Setting replicas to 0 stops all pods.

Using a string instead of a number.

The replicas field sets how many pod copies the ReplicaSet should maintain. Setting it to 5 means 5 pods will run to ensure availability.

2fill in blank

medium

Complete the selector to match pods with label app: nginx.

Kubernetes

selector:
  matchLabels:
    app: [1]

Drag options to blanks, or click blank then click option'

Amysql

Bredis

Cnginx

Dapache

Attempts:

3 left

💡 Hint

Common Mistakes

Using a label that does not match any pod.

Typos in label values.

The selector must match the pod label app: nginx so the ReplicaSet manages the correct pods.

3fill in blank

hard

Fix the error in the pod template labels to ensure they match the selector.

Kubernetes

template:
  metadata:
    labels:
      app: [1]

Drag options to blanks, or click blank then click option'

Amysql

Bapache

Credis

Dnginx

Attempts:

3 left

💡 Hint

Common Mistakes

Mismatch between selector and template labels.

Using different app names.

The pod template labels must match the selector labels exactly. Here, app: nginx ensures the ReplicaSet manages these pods.

4fill in blank

hard

Fill both blanks to complete the ReplicaSet spec that ensures 4 nginx pods.

Kubernetes

replicas: [1]
selector:
  matchLabels:
    app: [2]

Drag options to blanks, or click blank then click option'

A4

B3

Cnginx

Dapache

Attempts:

3 left

💡 Hint

Common Mistakes

Wrong number of replicas.

Selector label mismatch.

Setting replicas to 4 and selector app: nginx ensures 4 nginx pods run for availability.

5fill in blank

hard

Fill all three blanks to complete the pod template spec inside the ReplicaSet.

Kubernetes

template:
  metadata:
    labels:
      app: [1]
  spec:
    containers:
    - name: [2]
      image: [3]

Drag options to blanks, or click blank then click option'

Anginx

Bweb-server

Cnginx:latest

Dapache

Attempts:

3 left

💡 Hint

Common Mistakes

Mismatch between labels and container image.

Using wrong container names.

The pod template labels and container name should be consistent. Using app: nginx, container name web-server, and image nginx:latest ensures the ReplicaSet runs the correct pods.

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