Scaling Product Master instances

The Product Master service supports four standard installation sizes, which you can configure at the time of installation by using the custom resource. You can scale Product Master service based on usage to support high-availability, or increase processing capacity.

If the fixed T-shirt sizing is not appropriate or does not provide adequate capacity (for example, you need something bigger than the large configuration), you can use custom sizing by using Red Hat OpenShift Horizontal Pod Autoscaler (HPA).

To enable HPA after Product Master deployment,

Set the value of autoScaleConfig property as true in the CR file as follows.

cat <<EOF |oc apply -f
apiVersion: productmaster.cpd.ibm.com/v1
kind: ProductMaster
metadata:
  name: productmaster-cr
  labels:
    app.kubernetes.io/instance: ibm-cpd-productmaster-operator
    app.kubernetes.io/managed-by: ibm-cpd-productmaster-operator
    app.kubernetes.io/name: ibm-cpd-productmaster-operator
spec:
  version:  "10.0.0"
  scaleConfig: small
  license:
    accept: false
  shutdown: false
  #To enable HPA, autoScaleConfig should be set to true
  autoScaleConfig: <true/false>
  fileStorageClass: <file storage name>
  blockStorageClass: <block storage name>
EOF

Sizing details (Custom)

The following table shows the values (HPA name, Average utilization metric, Minimum replica, and Maximum replica) for each service to be specified for the respective T-shirt sizes.

T-shirt sizes		Small		Medium		Large		XLarge
HPA NAME	Average utilization metric	Minimum replica	Maximum replica	Minimum replica	Maximum replica	Minimum replica	Maximum replica	Minimum replica	Maximum replica
hpa-admin	70	1	5	2	7	2	9	2	11
hpa-personaui	70	1	5	2	5	2	5	2	5
hpa-ftsind	70	1	5	2	5	2	5	2	5
hpa-ftspim	70	1	5	2	5	2	5	2	5
hpa-wfl	70	1	5	2	7	2	9	2	11
hpa-sch	70	1	5	2	7	2	9	2	11
hpa-gds	70	1	5	2	5	2	5	2	5
hpa-ml	70	1	3	1	3	1	3	1	3
hpa-restapi	70	1	5	2	7	2	9	2	11