Persistent Volume (PV) requirements

Review the persistent volumes (PVs) required by your API Connect installation.

The PV requirements for API Connect subsystems vary according to the number of subsystem nodes that are deployed, whether you are using two datacenter disaster recovery (2DCDR) Two data center deployment strategy on Kubernetes and OpenShift, and other subsystem specific options.

Management subsystem

Table 1. Management PV requirements
Deployment profile Number of PVs required
Single node (n1) 3
Three node (n3) 7
Note: An additional 2 PVs are required for upgrade of the n3 deployment profile. Replaced PVs can be deleted after successful upgrade.

Gateway subsystem

Only required where tokenManagementService is enabled:

  tokenManagementService:
    enabled: true
    storage:
      storageClassName: $STORAGE_CLASS
      volumeSize: 30Gi

Portal subsystem

Table 2. Portal PV requirements
Deployment profile Number of PVs required
Single node (n1), one datacenter 6
Three nodes (n3), one datacenter 18
Single node (n1), two datacenter 9 per datacenter
Three nodes (n3), two datacenter 27 per datacenter
Single node (n1), two datacenter, where other datacenter is three node (n3) 13 in n1 datacenter, 23 in n3 datacenter
Three node (n3), two datacenter, where other datacenter is single node (n1) 30 in n3 datacenter, 15 in n1 datacenter

Analytics subsystem

The number of PVs needed varies according to whether the persistent queue feature is used, and if internal storage is enabled Planning to disable internal storage.
Table 3. Analytics PV requirements
Deployment profile Storage enabled Storage disabled (ingestion only) Extra PVs if persistent queue enabled
Single node (n1) 1 0 1
Three node (n3) 3 0 3
Note: The last column shows the PVs that must be added to those specified in the storage columns. For example, if you have an n1 profile with storage and persistent queue enabled, then you need 2 PVs.