Deploying Process Mining Custom Resource (CRD) with command-line tool

You can deploy a IBM Process Mining Custom Resource in the namespace using the Red Hat OpenShift command-line tool.

The following code displays a Custom Resource with the installation configuration set to default values. The only mandatory fields in this configuration are the acceptance of the license, the choice of Cloud Pak for license metering purpose, and the defaultStorage class that must be specified to a Red Hat OpenShift Storage class that supports Read/Write/Many mode. In the following example, the rook-cephfs storage is used, but you must specify a storage class available on your cluster.

cat <<EOF | oc apply -f -
apiVersion: processmining.ibm.com/v1beta1
kind: ProcessMining
metadata:
  name: processmining-instance
  namespace: ${PM_PROJECT}
spec:
  license:
    accept: true
    cloudPak: IBM Cloud Pak for Business Automation
  defaultStorageClassName: rook-cephfs
EOF

Through the CRD, you can customize the various installation options, for example, the type of storage, the size of storages, whether you use external databases and so on. The following CRD example displays some customization options for storage size:

cat <<EOF | oc apply -f -
apiVersion: processmining.ibm.com/v1beta1
kind: ProcessMining
metadata:
  name: processmining-instance
  namespace: ${PM_PROJECT}
spec:
  license:
    accept: true
    cloudPak: IBM Cloud Pak for Business Automation
  defaultStorageClassName: rook-cephfs
  taskmining:
    storage:
      events:
        name: processmining-repository
        size: '10'
      database:
        name: processmining-mongo
        size: '5'
  processmining:
    storage:
      database:
        class: 'ibmc-file-gold-gid'
        size: '5'
      events:
        name: taskminer-data
        size: '50'
    
EOF

For more information on custom resource definition, see CRD.