Access modes (ReadWriteOnce, ReadOnlyMany, ReadWriteMany) in Kubernetes - Cheat Sheet & Quick Revision

Recall & Review

beginner

What does the ReadWriteOnce access mode mean in Kubernetes?

ReadWriteOnce means the volume can be mounted as read-write by a single node only. It allows pods on one node to write and read the volume.

beginner

Explain the ReadOnlyMany access mode in Kubernetes.

ReadOnlyMany means the volume can be mounted as read-only by many nodes at the same time. Multiple pods can read from the volume but cannot write to it.

intermediate

What is the difference between ReadWriteMany and ReadWriteOnce?

ReadWriteMany allows multiple nodes to mount the volume as read-write simultaneously, while ReadWriteOnce allows only one node to mount it as read-write at a time.

beginner

Can a volume with ReadOnlyMany access mode be written to by pods?

No, pods can only read from a volume with ReadOnlyMany access mode. Writing is not allowed.

intermediate

Why is it important to choose the correct access mode for a PersistentVolume in Kubernetes?

Choosing the correct access mode ensures that pods can access the volume safely and as intended, preventing data corruption or access conflicts.

Which access mode allows a volume to be mounted as read-write by only one node?

A ReadOnlyOnce

B ReadOnlyMany

C ReadWriteMany

D ReadWriteOnce

ReadWriteOnce allows a volume to be mounted as read-write by a single node only.

If multiple pods need to read from the same volume but not write, which access mode should be used?

A ReadOnlyMany

B ReadWriteOnce

C ReadWriteMany

D WriteOnlyMany

ReadOnlyMany allows multiple nodes to mount the volume as read-only.

Which access mode supports multiple nodes mounting the volume as read-write simultaneously?

A ReadWriteOnce

B ReadOnlyMany

C ReadWriteMany

D ReadOnlyOnce

ReadWriteMany allows multiple nodes to mount the volume as read-write at the same time.

Can a volume with ReadWriteOnce be mounted by multiple nodes at the same time?

A No, only one node at a time

B Yes, but only read-only

C Yes, always

D Only if pods are on the same node

ReadWriteOnce restricts mounting as read-write to a single node at a time.

What happens if you try to write to a volume mounted with ReadOnlyMany?

A Write succeeds

B Write fails or is blocked

C Volume switches to read-write mode

D Pod crashes

Volumes mounted as ReadOnlyMany do not allow writing; attempts to write will fail or be blocked.

Describe the three Kubernetes access modes: ReadWriteOnce, ReadOnlyMany, and ReadWriteMany.

Think about how many nodes can access the volume and if they can write or only read.

Explain why selecting the correct access mode is important when configuring PersistentVolumes in Kubernetes.

Consider what happens if multiple pods write to the same volume incorrectly.

Practice

1. Which Kubernetes access mode allows a volume to be mounted as read-write by only one node at a time?

easy

A. ReadWriteOnce

B. ReadOnlyMany

C. ReadWriteMany

D. ReadWriteAll

Solution

1. Step 1: Understand ReadWriteOnce meaning

   ReadWriteOnce means the volume can be mounted as read-write by a single node only.

2. Step 2: Compare with other modes

   ReadOnlyMany allows multiple nodes but only read access; ReadWriteMany allows multiple nodes with read-write access.

3. Final Answer:

   ReadWriteOnce -> Option A

4. Quick Check:

   Single writer = ReadWriteOnce [OK]

Hint: Single writer means ReadWriteOnce [OK]

Common Mistakes:

• Confusing ReadWriteOnce with ReadWriteMany
• Thinking ReadOnlyMany allows write access
• Assuming ReadWriteAll is a valid mode

2. Which of the following is the correct YAML snippet to specify a volume with ReadOnlyMany access mode?

easy

A. accessModes:
- ReadWriteOnce

B. accessModes:
- ReadWriteMany

C. accessModes:
- ReadOnlyMany

D. accessModes:
- ReadOnlyOnce

Solution

1. Step 1: Identify correct access mode syntax

   The accessModes field is a list with valid values: ReadWriteOnce, ReadOnlyMany, ReadWriteMany.

2. Step 2: Match ReadOnlyMany exactly

   accessModes: - ReadOnlyMany correctly uses "ReadOnlyMany" as the access mode in YAML format.

3. Final Answer:

   accessModes:\n - ReadOnlyMany -> Option C

4. Quick Check:

   YAML list with ReadOnlyMany is correct [OK]

Hint: YAML list with dash and correct mode name [OK]

Common Mistakes:

• Using invalid mode ReadOnlyOnce
• Missing dash before access mode
• Using ReadWriteOnce instead of ReadOnlyMany

3. Given a PersistentVolumeClaim with accessModes set to [ReadWriteMany], what will happen if two pods on different nodes try to write to the volume simultaneously?

medium

A. Pods can only read, not write to the volume.

B. Only one pod can write; the other will get a write error.

C. The volume will be mounted read-only on both pods.

D. Both pods can write to the volume at the same time without issues.

Solution

1. Step 1: Understand ReadWriteMany behavior

   ReadWriteMany allows multiple nodes to mount the volume with read-write access simultaneously.

2. Step 2: Apply to pods on different nodes

   Since both pods are on different nodes, they can both write to the volume at the same time without conflict.

3. Final Answer:

   Both pods can write to the volume at the same time without issues. -> Option D

4. Quick Check:

   ReadWriteMany = multiple writers allowed [OK]

Hint: ReadWriteMany means multiple writers allowed [OK]

Common Mistakes:

• Assuming only one writer allowed with ReadWriteMany
• Confusing ReadOnlyMany with ReadWriteMany
• Thinking volume becomes read-only automatically

4. You have a PersistentVolumeClaim with accessModes set to ReadWriteOnce. You try to mount it as read-write on two pods running on different nodes. What is the likely outcome?

medium

A. Both pods mount the volume read-write successfully.

B. Only one pod mounts the volume read-write; the other fails to mount.

C. Both pods mount the volume read-only.

D. Both pods fail to mount the volume.

Solution

1. Step 1: Recall ReadWriteOnce limitation

   ReadWriteOnce allows only one node to mount the volume as read-write at a time.

2. Step 2: Analyze mounting on two nodes

   Since pods are on different nodes, only one pod can mount read-write; the other pod's mount will fail.

3. Final Answer:

   Only one pod mounts the volume read-write; the other fails to mount. -> Option B

4. Quick Check:

   ReadWriteOnce = single node writer [OK]

Hint: ReadWriteOnce limits to one node writer [OK]

Common Mistakes:

• Assuming both pods can mount read-write
• Thinking volume auto-switches to read-only
• Believing both pods fail to mount

5. You need to design a shared storage solution for a Kubernetes cluster where multiple pods across different nodes must read and write data simultaneously. Which access mode should you choose and why?

hard

A. ReadWriteMany, because it allows multiple pods on different nodes to read and write simultaneously.

B. ReadOnlyMany, because it allows multiple pods to write simultaneously.

C. ReadWriteOnce, because it supports multiple writers on different nodes.

D. ReadWriteOnce, because it allows multiple pods to read-only mount the volume.

Solution

1. Step 1: Identify requirement for multiple writers on different nodes

   The requirement is for multiple pods on different nodes to read and write simultaneously.

2. Step 2: Match access mode to requirement

   ReadWriteMany allows multiple nodes to mount the volume with read-write access at the same time, fulfilling the requirement.

3. Final Answer:

   ReadWriteMany, because it allows multiple pods on different nodes to read and write simultaneously. -> Option A

4. Quick Check:

   Shared read-write = ReadWriteMany [OK]

Hint: Multiple writers/readers need ReadWriteMany [OK]

Common Mistakes:

• Choosing ReadWriteOnce for multi-node writes
• Confusing ReadOnlyMany as write-capable
• Misunderstanding access mode capabilities