IBM Streams persistent volumes

Some IBM Streams features require the use of persistent storage.

A persistent volume (PV) is a Kubernetes resource that exists independently of resources (Kubernetes pods). The disk and data that is represented by a persistent volume continue to exist as resources are deleted and re-created. A persistent volume claim (PVC) is a request for and claim to a persistent volume resource.

By default, persistent volume claims are dynamically created by using the storage class that you specify when you install the Streams instance. Alternatively, you can manually create the persistent volume claims beforehand, and then specify the persistent volume claim names when you install the instance. For instructions for manually creating a pvc, see Creating a persistent volume for IBM Streams manually.

The persistent volume claims that are used by Streams are as follows:

Instance state persistent volume (instance.persistentVolumeClaim) - required

The instance state persistent volume contains the application cache and instance state data, which includes encoded application configuration objects, role information, the keystore and truststore, and the public key. For more information, see Configuring instance state persistent storage

Build service persistent volumes

Streams build service repository (builder.StreamsExtPvc) - optional: If you want to use Python or the Streams Flows app, this repository is required. Streams stores related files here. This repository can be shared by multiple Streams instances. The initial loading of this persistent volume can take a lot of time. If you intend to install multiple Streams instances, you can shorten the time required to create each instance by sharing this persistent volume.
Build-related data (build.persistentVolumeClaim) - required if you use the build service: This persistent volume contains build archives that are created by the Streams build service. For more information, see Customizing the build service to store build data.
External libraries and specialized toolkits (builder.persistentVolumeClaim) - optional: External libraries (that is, libraries that are not included in the Streams package) and specialized toolkits are stored on a persistent volume. For more information, see Customizing the build service to use specialized toolkits.

Security service persistent volume (security.persistentVolumeClaim) - required

The security service persistent volume stores state of the security service configuration.

Security-related persistent volume (security.userPersistentVolumeClaim) - optional

Custom login modules and custom login module code: For more information, see Developing user-defined login modules for the IBM Streams security service.
Note: This persistent volume claim must be manually created.
Streams auditing logging: For more information, see Enabling audit logging for IBM Streams
IBM Streams log: For more information about the IBM Streams log, see Log and trace files generated by IBM Streams.
Certificate revocation files: Certificate revocation files require a persistent volume when the Certificate Revocation List (CRL) security.revocationMethod is used. For more information, see Setting up client certificate revocation checking for IBM Streams users.