In IBM API Connect, which is part of IBM Cloud Pak for Integration (CP4I), the Management subsystem requires block storage with ReadWriteOnce (RWO) access mode.
The API Connect Management subsystem handles API lifecycle management, analytics, and policy enforcement.
It requires high-performance, low-latency storage, which is best provided by block storage.
The RWO (ReadWriteOnce) access mode ensures that each persistent volume (PV) is mounted by only one node at a time, preventing data corruption in a clustered environment.
Why "RWO Block Storage" is Required?Common Block Storage Options for API Connect on OpenShift:
Why the Other Options Are Incorrect?Option
Explanation
Correct?
A. NFS
❌ Incorrect – Network File System (NFS) is a shared file storage (RWX) and does not provide the low-latency performance needed for the Management subsystem.
❌
B. RWX block storage
❌ Incorrect – RWX (ReadWriteMany) block storage is not supported because it allows multiple nodes to mount the volume simultaneously, leading to data inconsistency for API Connect.
❌
D. GlusterFS
❌ Incorrect – GlusterFS is a distributed file system, which is not recommended for API Connect’s stateful, performance-sensitive components.
❌
Final Answer:✅ C. RWO block storage
IBM API Connect System Requirements
IBM Cloud Pak for Integration Storage Recommendations
Red Hat OpenShift Storage Documentation
IBM Cloud Pak for Integration (CP4I) v2021.2 Administration References:
