Creating volumes and folders for deployment
The FNCM component containers require some persistent volumes, persistent volume claims, and folders to be created before you can deploy. The deployment process uses these volumes and folders during the deployment. The following steps cover static provisioning of the persistent volumes and persistent volume claims.
Before you begin
About this task
You can choose to have the operator dynamically provision storage for you at deployment time. In that case, you do not need to create volumes and folders manually for your container environment. You can maintain the default storage values for your FNCM components in the custom resource YAML.
- If the claim does not exist, dynamic provisioning is used. When the claim is created, the persistent volume claim names that are provided in the custom resource YAML are used.
- If the claim does exist, that claim is used during deployment.
- If static provisioning is used, you need to pre-create the persistent volumes and persistent volume claims and provide the persistent volume claim name in the CR.
If you want to use statically provisioned configuration for your storage, use the steps in mentioned in the following procedure.
accessModes: ReadWriteMany
persistentVolumeReclaimPolicy: Retain
The reclaim policy must be specified as Retain
for persistent volumes that
store data. It includes the persistent volume that is created for the
cpe-filestore-pvc
and css-indexstore-pvc
. For dynamically created
volumes, the storage class that is specified must be configured with a Retain
reclaim policy to have a reclaim policy of retain. Other PVCs can optionally be configured with
Retain if the contents of the volume are difficult to reconstruct. For example, the location where
binaries might be uploaded such as the cpe-cfgstore-pvc
or
icn-pluginstore-pvc
.
- When during a major version upgrade, you want to deploy your existing data and configuration in a new environment that uses a new namespace.
- Or, when you want to recover a preexisting FileNet P8 domain by deploying the same version of FNCM to a new namespace, in a new cluster.
chmod -R g+rw
The persistent volume names, path, and size that are provided in the following tables are examples. During deployment, the FNCM operator looks for the provided persistent volume claim names as the default.