Update PV Access Modes table: Reflect RWX support for FC and iSCSI in volumeMode: BlockPersistent Volumes

[jscc-hv]

Page URL: https://kubernetes.io/docs/concepts/storage/persistent-volumes/#access-modes

Description:
The "Access Modes" table currently lists Fibre Channel (FC) and iSCSI as not supporting ReadWriteMany (RWX). This is inaccurate for volumeMode: Block.

Enterprise CSI drivers (e.g., Hitachi, NetApp Trident, Dell, Pure Storage) support RWX for FC and iSCSI when presented as raw block devices. This configuration is a requirement for KubeVirt live migration and clustered applications.

Proposed Change:
Update the FC and iSCSI rows in the Volume Plugins table to show RWX support for Block mode.

Suggested Note:
"RWX is supported for FC and iSCSI when using volumeMode: Block via a compatible CSI driver."

Additional Context:
The current "No" in the RWX column reflects legacy "In-Tree" plugin limitations and filesystem safety. It does not reflect the capabilities of these protocols at the block layer in modern CSI implementations.

---

Labels: sig/storage, area/documentation

[k8s-ci-robot]

This issue is currently awaiting triage.

SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the triage/accepted label.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[ArushKachru]

Hi,

I went ahead and updated the "Access Modes" table to reflect that FC and iSCSI can support ReadWriteMany (RWX) when used with volumeMode: Block and a compatible CSI driver.

I also added a note clarifying that this behavior differs from legacy in-tree plugin limitations and depends on the underlying CSI driver.

I’ve submitted a PR with this change. Please let me know if you have any suggestions or if there’s anything you’d like me to adjust. Thanks

[jscc-hv]

Hi @ArushKachru, thank you for your responsiveness. I don't have anything else for suggestions. Thanks again