Scaling manually

You can configure the number of replicas for Decision Center, Decision Runner, and Decision Server Runtime.

About this task

If a deployment is exposed publicly when you change the number of replicas, the service distributes the traffic to the available pods during the update. An available pod is an instance that can be accessed by users.

Procedure

From the Kubernetes command line, you set the scale value by using the replicas parameter. 
kubectl scale --replicas=2 deployment/odm-instance-odm-decisionrunner
Where odm-instance-odm-decisionrunner is the name of the deployment you want to scale.

It is also possible to specify one or more preconditions for the scale action. If either of the current-replicas or resource-version parameters are specified, they are validated before the scale is attempted. The precondition must hold true for the scale to be applied to the server. For more information, see kubectl scale External link opens a new window or tab.

Note: If autoscaling is enabled for one of the components, the value set for the parameter replicaCount is ignored. For more information, see Autoscaling.

You can also set the replicaCount parameter at installation time, for example with --set decisionServerRuntime.replicaCount=2 to configure Decision Server Runtime to use two replicas.

Results

You can check the scaling of the deployment with the following command.

$ kubectl get replicaset
NAME                                               DESIRED           CURRENT            READY         AGE
odm-instance-odm-decisioncenter-6dbdc7dc76         1                 1                  1             20m
odm-instance-odm-decisionrunner-69bd849dc7         1                 1                  1             20m
odm-instance-odm-decisionserverconsole-7495b7f8cd  1                 1                  1             20m
odm-instance-odm-decisionserverruntime-7b599d754   2                 2                  2             20m
Where:
  • DESIRED is the desired number of replicas of a pod, which you define when you create the deployment
  • CURRENT is the number of replicas currently running
  • READY is the number of replicas that are available to the users compared to the desired state