A city batch Job must read shared CSV files from a PVC while several worker Pods run at once. Writers elsewhere already finished the data. Which consume-side access mode should the Job’s PVC request?
Select an answer to reveal the explanation.
Short Explanation
Picture a shared binder of finished CSVs on a library cart—everyone can flip through, nobody needs a pen. ReadOnlyMany lets many Job Pods mount that finished data for reads without fighting over writers. Exclusive write modes are the wrong gear for a read-only consume pattern.
Full Explanation
When an application only needs concurrent read access to shared files, ReadOnlyMany (ROX) is the appropriate PVC access mode on the consume side. ReadWriteOnce limits attachment to a single node and implies write intent; ReadWriteMany allows multi-writer contention that this Job does not need. Application developers choose accessModes that match the workload’s read/write pattern rather than inventing StorageClasses.