storage parameter

Use storage to configure the persistent volume for shared storage.
  • The storageconfiguration is used to identify an existing Persistent Volume Claim (PVC) with the given name or create a new PVC with this name if it does not exist.
  • The parameters of the PVC must match with the parameters of the PV created in the Creating a Kubernetes Persistent Volume manually page.
The following YAML snippet is a sample schema of storage:
  storage:
    name: ""
    # accessMode: ReadWriteMany
    # capacity: 10Gi
    # storageClassName: default
The following table explains the attributes applicable for the storage parameter of SIPEnvironment.
Property Default value Value type Required Description
name   string Yes Specify the name of the Persistent Volume Claim (PVC). If the PVC doesn’t exist, a new PVC is created and expected to be bound. If the PVC exist, then it is reused.
accessMode ReadWriteMany string No Specify the access mode for the Persistent Volume as ReadWriteMany. This is required for use with features such as search catalog index, where multiple pods such as appServers and agentServers can read or write from this shared persistent volume.
capacity 10Gi string or integer No Specify the capacity for the Persistent Volume.
storageClassName default string No Specify the storage class for the Persistent Volume Claim.

Option to create Persistent Volume Claims manually

You can manually create the required Persistent Volume Claims (PVCs) before installing Sterling Intelligent Promising. However, if the PVCs are not created in advance, Sterling Intelligent Promising automatically creates the necessary PVCs as defined in the SIPEnvironment YAML during installation.

Attention: Sterling Intelligent Promising does not create the corresponding Persistent Volumes (PVs). You must ensure that the required PVs are created and correctly bound to the PVCs. If matching PVs are not available, the PVCs remain in a Pending state, which can lead to installation or runtime issues. For more information, see Creating a Kubernetes Persistent Volume manually.