StatefulSet ordering and naming in Kubernetes - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Pod Naming Pattern in StatefulSets

In Kubernetes StatefulSets, what is the correct naming pattern for pods created by a StatefulSet named web with 3 replicas?

A web-0, web-2, web-4

B web-1, web-2, web-3

C web-0, web-1, web-2

D web-01, web-02, web-03

💡 Hint

Pods are named with the StatefulSet name plus a zero-based ordinal index.

StatefulSet pods are named using the StatefulSet name followed by a dash and a zero-based ordinal number starting at 0.

💻 Command Output

intermediate

Pod Creation Order in StatefulSets

What is the order of pod creation when a StatefulSet with 3 replicas is deployed?

Kubernetes

kubectl get pods -l app=web --watch

A web-0, web-1, web-2 in sequence

B All pods created simultaneously

C web-2, web-1, web-0 in sequence

D web-1, web-0, web-2 in sequence

💡 Hint

StatefulSets create pods one by one in order.

StatefulSets create pods sequentially starting from ordinal 0 to the highest ordinal.

🔀 Workflow

advanced

Pod Deletion and Recreation Order

If you delete pod web-1 in a StatefulSet with 3 replicas, what happens next?

A All pods are deleted and recreated

B web-2 is deleted and recreated before web-1

C web-0 is deleted and recreated before web-1

D Only web-1 is recreated immediately

💡 Hint

Pods are managed individually but respect ordinal order on creation.

Deleting a pod causes only that pod to be recreated. StatefulSet does not delete other pods automatically.

❓ Troubleshoot

advanced

Pod Naming Conflict in StatefulSet

You manually create a pod named web-1 in the same namespace as a StatefulSet named web. What problem can this cause?

A The manual pod is automatically adopted by the StatefulSet

B StatefulSet controller cannot create its own web-1 pod, causing a stuck pod

C StatefulSet deletes the manual pod and creates its own

D No problem, StatefulSet ignores manually created pods

💡 Hint

StatefulSet expects to control pods with specific names.

Manually creating a pod with a StatefulSet pod name blocks the StatefulSet controller from creating its pod, causing issues.

✅ Best Practice

expert

Ensuring Stable Network IDs with StatefulSets

Which practice ensures stable network identities for pods in a StatefulSet?

A Use a Headless Service with the same name as the StatefulSet

B Use a ClusterIP Service with selectors matching the StatefulSet

C Use a LoadBalancer Service for external access

D Use a DaemonSet instead of StatefulSet

💡 Hint

Stable network IDs require DNS entries per pod.

A Headless Service without a cluster IP creates DNS entries for each pod, giving stable network IDs matching pod names.

Practice

1. What is a key feature of a Kubernetes StatefulSet compared to a Deployment?

easy

A. Pods share the same IP address at all times.

B. Pods have stable, unique network identities and persistent storage.

C. Pods are created and deleted randomly without order.

D. Pods cannot be scaled after creation.

Solution

1. Step 1: Understand StatefulSet purpose

   StatefulSets provide stable network IDs and persistent storage for pods, unlike Deployments.

2. Step 2: Compare with Deployment behavior

   Deployments create pods without stable names or guaranteed order, while StatefulSets do.

3. Final Answer:

   Pods have stable, unique network identities and persistent storage. -> Option B

4. Quick Check:

   StatefulSet = stable pods and storage [OK]

Hint: StatefulSet = stable pod names and storage [OK]

Common Mistakes:

• Thinking StatefulSet pods have random names
• Assuming StatefulSet pods share IPs
• Believing StatefulSets cannot scale

2. Which of the following is the correct naming pattern for pods created by a StatefulSet named web with 3 replicas?

easy

A. web-01, web-02, web-03

B. web-1, web-2, web-3

C. web-0, web-2, web-4

D. web-0, web-1, web-2

Solution

1. Step 1: Recall StatefulSet pod naming

   Pods are named as {statefulset-name}-{ordinal} starting at 0.

2. Step 2: Apply to given example

   For 3 replicas, pods are web-0, web-1, and web-2.

3. Final Answer:

   web-0, web-1, web-2 -> Option D

4. Quick Check:

   StatefulSet pods start at 0 [OK]

Hint: Pod names start at 0 and increment by 1 [OK]

Common Mistakes:

• Starting pod names at 1 instead of 0
• Skipping ordinals or using even numbers only
• Using zero-padded numbers like 01

3. Given a StatefulSet named db with 2 replicas, what will be the order of pod termination when scaling down from 2 to 1 replica?

medium

A. db-1 terminates first, then db-0

B. db-0 terminates first, then db-1

C. Both pods terminate simultaneously

D. Pods terminate in random order

Solution

1. Step 1: Understand StatefulSet termination order

   StatefulSets terminate pods in reverse ordinal order when scaling down.

2. Step 2: Apply to example

   With pods db-0 and db-1, db-1 (highest ordinal) terminates first.

3. Final Answer:

   db-1 terminates first, then db-0 -> Option A

4. Quick Check:

   Pods terminate highest ordinal first [OK]

Hint: Pods terminate highest ordinal first when scaling down [OK]

Common Mistakes:

• Assuming pods terminate in creation order
• Thinking pods terminate simultaneously
• Believing termination order is random

4. You have a StatefulSet with 3 replicas named cache. You notice pods cache-2 is stuck terminating and blocking scale down. What is a likely cause?

medium

A. Pod cache-2 has a finalizer preventing deletion.

B. Pod cache-0 is still running and blocking cache-2.

C. StatefulSet does not support scaling down pods.

D. Pod names must be numeric only without dashes.

Solution

1. Step 1: Identify common pod termination issues

   Pods stuck terminating often have finalizers or resources blocking deletion.

2. Step 2: Apply to StatefulSet pod cache-2

   Pod cache-2 likely has a finalizer preventing its deletion, causing the block.

3. Final Answer:

   Pod cache-2 has a finalizer preventing deletion. -> Option A

4. Quick Check:

   Finalizers block pod deletion [OK]

Hint: Check for finalizers if pod stuck terminating [OK]

Common Mistakes:

• Thinking lower ordinal pods block higher ones
• Believing StatefulSets cannot scale down
• Misunderstanding pod naming rules

5. You want to deploy a StatefulSet with 3 replicas but require pods to start in parallel instead of sequentially. Which field should you modify to achieve this?

hard

A. Set serviceName to empty string.

B. Set replicaCount: 3 in the pod template.

C. Set podManagementPolicy: Parallel in the StatefulSet spec.

D. Set updateStrategy: RollingUpdate in the StatefulSet spec.

Solution

1. Step 1: Understand podManagementPolicy in StatefulSets

   By default, StatefulSets create pods sequentially. Setting podManagementPolicy to Parallel allows parallel pod creation.

2. Step 2: Identify correct field to change

   Changing podManagementPolicy to Parallel in the spec enables parallel pod startup.

3. Final Answer:

   Set podManagementPolicy: Parallel in the StatefulSet spec. -> Option C

4. Quick Check:

   podManagementPolicy controls pod start order [OK]

Hint: Use podManagementPolicy: Parallel to start pods together [OK]

Common Mistakes:

• Changing replicaCount instead of podManagementPolicy
• Confusing updateStrategy with pod start order
• Removing serviceName breaks network identity