Access mode
An access mode is a persistent-storage policy specifying how and by how many nodes or Pods a volume may be mounted for reading and writing.
Kubernetes in Action, Second Edition
An access mode is a PersistentVolume and PersistentVolumeClaim specification describing how a volume may be mounted by nodes or pods for reading and writing.
- How it is used
- Specifies the requested read/write sharing pattern when a PersistentVolumeClaim obtains storage for pods.
- How deep it goes
- Distinguishes four modes by pod, node, and read/write access, then demonstrates scheduling and attachment failures; does not detail storage-driver internals.
- Examples
- Uses a 1Gi claim, competing quiz pods, and same-node versus different-node pods to show the modes’ effects.
- What you can do after
- Apply it via PersistentVolumeClaim manifests to request a sharing pattern and diagnose pod attachment problems with kubectl.
Read how Kubernetes in Action, Second Edition explains access mode →
Acing the Certified Kubernetes Administrator Exam, Second Edition
An access mode is a storage configuration specifying how many pods may read from or write to a volume.
- How it is used
- Selects the node or pod access pattern required when binding persistent storage to applications.
- How deep it goes
- Distinguishes four modes, PV/PVC selection rules, and volume compatibility, without detailing storage-driver internals.
- Examples
- Uses RWO, ROX, RWX, and RWOP examples, contrasting hostPath, nfs, and emptyDir behavior.
- What you can do after
- Configure storage access by selecting a supported mode based on node count and read/write requirements.
Read how Acing the Certified Kubernetes Administrator Exam, Second Edition explains access mode →
Kubernetes for Developers
An access mode specifies how and by how many Pods a persistent volume may be mounted for reading and writing.
- How it is used
- Guides PersistentVolumeClaim storage choices for stateful Pods and determines whether volumes support single- or multi-Pod access.
- How deep it goes
- Defines three access modes and their storage implications, but defers provisioning behavior to StorageClass configuration.
- Examples
- Uses a MariaDB Pod with a 2 GiB ReadWriteOnce claim mounted at /var/lib/mysql.
- What you can do after
- Configure a PersistentVolumeClaim with an access mode suited to the workload's Pod count and storage type.
Related concepts
- readwriteonceincludes · ReadWriteOnce is a Kubernetes persistent-storage access mode allowing a volume to be mounted for read-write use by a single node.
- readonlymanyincludes · ReadOnlyMany is a Kubernetes volume access mode allowing a volume to be mounted concurrently as read-only by multiple nodes or pods.
- readwritemanyincludes · ReadWriteMany is a Kubernetes volume access mode allowing a volume to be mounted concurrently as read-write by multiple nodes or pods.
- persistent volumeconfigures · A persistent volume is durable storage provisioned independently of an individual workload’s lifecycle, allowing data to survive workload replacement or restart.
- emptydir volumecontrasts with · An emptyDir volume is a Kubernetes volume that starts empty, is available to containers in a Pod, and is deleted when the Pod leaves its node.
- ReadWriteOncePodincludes · ReadWriteOncePod is a Kubernetes volume access mode allowing a volume to be mounted read-write by only one pod at a time.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.