Manually scaling resources for services

You can adjust IBM® Software Hub services by scaling the resources that they use to support high availability or to increase processing capacity. Resources can be scaled based on predefined resource configurations.

Permissions that you need for this task

You must be either:

A cluster administrator
An instance administrator

When you need to complete this task

If a service supports scaling, you can scale the service at any time after you install it.

Using the web client to scale services

You can set the scaling configuration level for services by using the web client. In the web client, you can check the current scaling configuration level for a service, and you can change the scaling configuration level at the same time.

Important: Only services that use the scale setting to set the scaling configuration level can be scaled through the web client.

Scaling changes the capacity of services by adjusting the memory resource settings, the number of CPUs, and the number of pods that are available.

Use the scale setting for the service to set the scaling configuration level.

The following table provides information about when to use each of the scale settings. Some services might not support all scale settings included in the table.

Scale setting	Description
Level 1 Minimal CPU reservation	When you use this setting, pods are configured so that minimal CPU resources are reserved on the cluster. However, growth is constrained to a configured maximum. This setting is appropriate for environments with low concurrency where you want to free up CPU resources when the service is inactive for long periods of time. This setting does not guarantee resiliency through redundant pod replicas.
Level 2 Small workloads Resiliency not guaranteed	When you use this setting, pods are configured with the minimum recommended footprint. Some pods grow to consume more CPU resources when they are active. However, growth is constrained to a configured maximum. This setting is appropriate for environments with low concurrency. This setting does not guarantee resiliency through redundant pod replicas.
Level 3 Resiliency and concurrency	When you use this setting, the service can handle moderate workloads with a reasonable level of redundancy for resilience.
Level 4 High availability with large workloads	When you use this setting, the service can handle larger workloads and more users with better resiliency. With this setting, the service is more likely to remain available when failures or disruptions occur.
Level 5 High availability with large workloads and more concurrency	When you use this setting, the service can handle substantial workloads and many concurrent users with resiliency and redundancy. With this setting, the service is more likely to remain available when failures or disruptions occur.

Tip: Detailed information about the various sizes is available in the Component scaling guidance PDF document. The PDF is in the IBM Entitled Registry. For details, see Downloading the component scaling guidance PDF from the IBM Entitled Registry.

Most services use the cpd-cli manage apply-scale-config command to set the scale setting. For a few services, you use the cpd-cli manage apply-cluster-component-scale-config command to set the scale setting.

Some services support scaling but do not support the use of the cpd-cli manage apply-scale-config command. These services use different methods.

The following table shows the services that support manual scaling and the method used for scaling. Click a service name or scroll to the procedure for manually scaling services for detailed instructions about how to scale each service.

Service name	Uses the scale setting	Uses a different scaling method
IBM Software Hub control plane	✓	Not supported
Canvas	✓	Not supported
Common core services	✓	Not supported
IBM Cloud Pak foundational services	✓	Not supported
Inference foundation models	✓	Not supported
AI Factsheets	✓	Not supported
Analytics Engine powered by Apache Spark	✓	Not supported
Cognos Analytics	Not supported	✓
Cognos Dashboards	✓	Not supported
Data Gate	✓	Not supported
Data Privacy	✓	Not supported
Data Product Hub	✓	Not supported
Data Refinery	✓	Not supported
Data Replication	✓	Not supported
DataStage	✓	Not supported
Data Virtualization	Not supported	✓
Db2	Not supported	✓
Db2 Big SQL	Not supported	✓
Db2 Data Management Console	✓	Not supported
Db2 Warehouse	Not supported	✓
Decision Optimization	✓	Not supported
EDB Postgres	Not supported	Not supported
Execution Engine for Apache Hadoop	✓	Not supported
Unstructured Data Integration	✓	Not supported
IBM Knowledge Catalog (all editions)	✓	Not supported
IBM Manta Data Lineage	✓	Not supported
IBM Master Data Management	✓	Not supported
IBM StreamSets	Not supported	Not supported
Informix	Not supported	✓
MANTA Automated Data Lineage	✓	Not supported
OpenPages	✓	Not supported
Orchestration Pipelines	✓	Not supported
Planning Analytics	Not supported	✓
Product Master	✓	Not supported
RStudio® Server Runtimes	Not supported	Not supported
Scheduling service	✓	Not supported
SPSS Modeler	✓	Not supported
Synthetic Data Generator	See Canvas	Not supported
Voice Gateway	Not supported	✓
Watson Discovery	✓	Not supported
Watson Machine Learning	✓	Not supported
Watson OpenScale	✓	Not supported
Watson Speech services	Not supported	✓
Watson Studio	✓	Not supported
Watson Studio Runtimes	Not supported	Not supported
watsonx.ai™	✓	Not supported
watsonx Assistant	✓	Not supported
watsonx™ BI	Not supported	Not supported
watsonx Code Assistant™	✓	Not supported
watsonx Code Assistant for Red Hat® Ansible® Lightspeed	✓	Not supported
watsonx Code Assistant for Z Agentic	✓	Not supported
watsonx Code Assistant for Z Understand	✓	Not supported
watsonx.data™	✓	Not supported
watsonx.data integration	Not supported for the service but supported for the following tools: Data Observability Data Replication DataStage	Not supported
watsonx.data intelligence	✓
watsonx.data Premium	✓	Not supported
watsonx.governance™	Not supported	✓
watsonx Orchestrate	✓	Not supported

Before you begin

Best practice: You can run the commands in this task exactly as written if you set up environment variables. For instructions, see Setting up installation environment variables.

Ensure that you source the environment variables before you run the commands in this task.

Before you scale up a service, ensure that your cluster can support the additional workload. If necessary, contact your IBM Support representative.

When you change the scaling configuration level of a service, you also must scale the related services. For more information about service dependencies, see Service software requirements.

For the cpd-cli command, you can scale the services individually, or you can scale several services at the same time by using the --components option. Specify a comma-separated list of component names to set all the components to the same level, for example:

--components=zen,dp,ws \
--scale=level_3

If you want to scale a service that does not use the default custom resource name, you must use the --param-file option to override the custom resource name.

Create a .yml file that has the following content:

override_components_meta:
    component-name:
        cr_name: your-cr-name

Add --param-file=/tmp/work/filename.yml to the cpd-cli command.

You can also set the --wait option to false to save time. When --wait=false the custom resource is patched, but the cpd-cli returns you to a command prompt without waiting for the cpd-cli to get to a Completed state.

Procedure

If you want to check the current scale setting, use the manage get-scale-config command.
Note: Scheduling service uses the manage get-cluster-component-scale-config command instead.
For example, to check the scale setting for the common core services and Canvas, use this command:
```
cpd-cli manage get-scale-config \
--cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \
--components=ccs,canvasbase
```
Complete the steps for the service that you are scaling:
IBM Software Hub control plane
1. Set the SCALE environment variable to the appropriate level for your environment.
```
export SCALE=<level>
```
2. Run the following command to scale the component by updating the custom resource::
```
cpd-cli manage apply-scale-config \
--cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \
--components=zen \
--scale=${SCALE}
```
Canvas
Canvas is a dependency for the following services:
- SPSS Modeler. If you want to scale SPSS Modeler, you must scale Canvas as well.
- Synthetic Data Generator. If you want to scale Synthetic Data Generator, you must scale Canvas.
1. Set the SCALE environment variable to the appropriate level for your environment.
```
export SCALE=<level>
```
2. Run the following command to scale the component by updating the custom resource:
```
cpd-cli manage apply-scale-config \
--cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \
--components=canvasbase \
--scale=${SCALE}
```
Common core services
1. Set the SCALE environment variable to the appropriate level for your environment.
```
export SCALE=<level>
```
2. If you want to scale the common core services, run the following command to update the custom resource:
```
cpd-cli manage apply-scale-config \
--cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \
--components=ccs \
--scale=${SCALE}
```
3. If you want to scale Flight service, update the custom resource by using a parameter file to override the scale_config_field to flightScaleConfig:
  1. Create a parameter file /tmp/work/override.yaml, and add the following text:
    override_components_meta: ccs: scale_config_field: flightScaleConfig
  2. Run the following command using the parameter file:
    cpd-cli manage apply-scale-config \ --cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \ --components=ccs \ --scale=${SCALE} \ --param-file=/tmp/work/override.yaml
IBM Cloud Pak foundational services
1. Set the SCALE environment variable to the appropriate level for your environment.
```
export SCALE=<level>
```
2. Run the following command to scale the component by updating the custom resource:
```
cpd-cli manage apply-scale-config \
--cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \
--components=cpfs \
--scale=${SCALE}
```
Inference foundation models
1. Set the SCALE environment variable to the appropriate level for your environment.
```
export SCALE=<level>
```
2. Run the following command to scale the component by updating the custom resource:
```
cpd-cli manage apply-scale-config \
--cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \
--components=watsonx_ai_ifm \
--scale=${SCALE}
```
AI Factsheets
1. Set the SCALE environment variable to the appropriate level for your environment.
```
export SCALE=<level>
```
2. Run the following command to scale the component by updating the custom resource:
```
cpd-cli manage apply-scale-config \
--cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \
--components=factsheet \
--scale=${SCALE}
```
Analytics Engine powered by Apache Spark
1. Set the SCALE environment variable to the appropriate level for your environment.
```
export SCALE=<level>
```
2. Run the following command to scale the component by updating the custom resource:
```
cpd-cli manage apply-scale-config \
--cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \
--components=analyticsengine \
--scale=${SCALE}
```
Cognos Analytics
When you provision a Cognos Analytics service instance, you choose a size for the instance. The following sizes are supported:
- fixed minimum (no scale)
- xsmall
- small_mincpureq
  Use this setting when you want to use minimal reserved CPU resources without removing the CPU pod setting.
- small
- medium
- large
For more information about scaling a service instance, see Provisioning the Cognos Analytics service.

You can also change the size of the instance after it is already provisioned. For more information, see Changing the plan size of the Cognos Analytics service instance.
Cognos Dashboards
1. Set the SCALE environment variable to the appropriate level for your environment.
```
export SCALE=<level>
```
2. Run the following command to scale the component by updating the custom resource:
```
cpd-cli manage apply-scale-config \
--cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \
--components=dashboard \
--scale=${SCALE}
```
Data Gate

To scale a Data Gate instance, you must choose a size for the instance. The following sizes are supported:
1. small_mincpureq (default)
2. small (default)
3. medium
4. large
For more information about scaling Data Gate, see Scaling the Data Gate instance.
Unstructured Data Integration
1. Set the SCALE environment variable to the appropriate level for your environment.
```
export SCALE=<level>
```
2. Run the following command to scale the component by updating the custom resource:
```
cpd-cli manage apply-scale-config \
--cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \
--components=udp \
--scale=${SCALE}
```
Data Privacy
1. Set the SCALE environment variable to the appropriate level for your environment.
```
export SCALE=<level>
```
2. Run the following command to scale the component by updating the custom resource:
```
cpd-cli manage apply-scale-config \
--cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \
--components=dp \
--scale=${SCALE}
```
Data Product Hub
1. Set the SCALE environment variable to the appropriate level for your environment.
```
export SCALE=<level>
```
2. Run the following command to scale the component by updating the custom resource:
```
cpd-cli manage apply-scale-config \
--cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \
--components=dataproduct \
--scale=${SCALE}
```
Data Refinery
1. Set the SCALE environment variable to the appropriate level for your environment.
```
export SCALE=<level>
```
2. Run the following command to scale the component by updating the custom resource:
```
cpd-cli manage apply-scale-config \
--cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \
--components=datarefinery \
--scale=${SCALE}
```
Data Replication
1. Set the SCALE environment variable to the appropriate level for your environment.
```
export SCALE=<level>
```
2. Run the following command to scale the component by updating the custom resource:
```
cpd-cli manage apply-scale-config \
--cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \
--components=replication \
--scale=${SCALE}
```
DataStage
1. Set the SCALE environment variable to the appropriate level for your environment.
```
export SCALE=<level>
```
2. Run the following command to scale the component by updating the custom resource:
```
cpd-cli manage apply-scale-config \
--cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \
--components=datastage_ent \
--scale=${SCALE}
```
Data Virtualization
You can scale the Data Virtualization service instance. You cannot use the scale setting to directly scale Data Virtualization. However, you can use the scale setting to scale the bigsql db2u-dv CR in the Data Virtualization instance.
For more information about the process for scaling Data Virtualization, see Scaling Data Virtualization.

Db2

To scale Db2, work with your IBM Sales representative to size your cluster.

For more information about scaling Db2, see Scaling up Db2.

Db2 Big SQL

You can scale a Db2 Big SQL service instance from the instance details page in the IBM Software Hub web client.

For information about scaling Db2 Big SQL, see Configuring a Db2 Big SQL instance.
Db2 Data Management Console
1. Set the SCALE environment variable to the appropriate level for your environment.
```
export SCALE=<level>
```
2. Run the following command to scale the component by updating the custom resource:
```
cpd-cli manage apply-scale-config \
--cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \
--components=dmc \
--scale=${SCALE}
```
Db2 Warehouse

To scale Db2 Warehouse, work with your IBM Sales representative to size your cluster.

For more information about scaling Db2 Warehouse, see Scaling Db2 Warehouse.
Decision Optimization
1. Set the SCALE environment variable to the appropriate level for your environment.
```
export SCALE=<level>
```
2. Run the following command to scale the component by updating the custom resource:
```
cpd-cli manage apply-scale-config \
--cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \
--components=dods \
--scale=${SCALE}
```
Execution Engine for Apache Hadoop
1. Set the SCALE environment variable to the appropriate level for your environment.
```
export SCALE=<level>
```
2. Run the following command to scale the component by updating the custom resource:
```
cpd-cli manage apply-scale-config \
--cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \
--components=hee \
--scale=${SCALE}
```
IBM Knowledge Catalog
IBM Knowledge Catalog is available in three different editions. You must specify the edition when you scale the service.
Important: If you scale up IBM Knowledge Catalog, for example to level_3(medium), it increases the number of Neo4j cluster primaries. However, you cannot scale the number of Neo4j cluster back down once increased. This limitation prevents data integrity issues.
1. Set the IKC_TYPE environment variable to the edition of IBM Knowledge Catalog that is installed:
  IBM Knowledge Catalog
  
  export IKC_TYPE=wkc
  IBM Knowledge Catalog Premium
  
  export IKC_TYPE=ikc_premium
  IBM Knowledge Catalog Standard
  
  export IKC_TYPE=ikc_standard
2. Set the SCALE environment variable to the appropriate level for your environment.
  export SCALE=<level>
3. Run the following command to scale the component by updating the custom resource:
  cpd-cli manage apply-scale-config \ --cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \ --components=${IKC_TYPE} \ --scale=${SCALE}
IBM Manta Data Lineage
1. Set the SCALE environment variable to the appropriate level for your environment.
```
export SCALE=<level>
```
2. Run the following command to scale the component by updating the custom resource:
```
cpd-cli manage apply-scale-config \
--cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \
--components=datalineage \
--scale=${SCALE}
```
IBM Master Data Management
1. Set the SCALE environment variable to the appropriate level for your environment.
  export SCALE=<level>
2. Run the following command to scale the component by updating the custom resource:
  cpd-cli manage apply-scale-config \ --cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \ --components=match360 \ --scale=${SCALE}
Informix

Informix does not support the scale setting to scale the service instance.

Use the following steps to adjust the amount of CPU and memory that are allocated to an Informix service instance:
1. Go to the Informix instance details page in the IBM Software Hub web client.
  1. Get the deployment ID of the instance.
  2. Review the current configuration to determine the number of nodes, the number of cores, and the amount of memory allocated to the instance.
2. Run the following command to set the INSTANCE_ID environment variable:
```
export INSTANCE_ID=<instance-id>
```
3. Run the following command to scale the number of Informix servers in the service instance:
```
oc patch Informixes informix-${INSTANCE_ID} \
--namespace ${PROJECT_CPD_INST_OPERANDS}
--patch '{"spec":{"replicas":2}}' \
--type=merge
```
4. To increase the CPU or memory that the service instance can use, run the appropriate command:
  Increase memory limits
  
  The following example sets the memory limits to 4 GiB.
  
  oc patch Informixes informix-${INSTANCE_ID}-server \ --namespace ${PROJECT_CPD_INST_OPERANDS} \ --patch '{"spec":{"resources":{"limits":{"memory":"4Gi"}}}}' \ --type=merge
  
  Increase memory
  
  The following example sets the memory requests to 2 GiB.
  
  oc patch Informixes informix-${INSTANCE_ID}-server \ --namespace ${PROJECT_CPD_INST_OPERANDS} \ --patch '{"spec":{"resources":{"requests":{"memory":"2Gi"}}}}' \ --type=merge
  
  Increase CPU limits
  
  The following example sets the CPU limits to 4 CPU.
  
  oc patch Informixes informix-${INSTANCE_ID}-server \ --namespace ${PROJECT_CPD_INST_OPERANDS} \ --patch '{"spec":{"resources":{"limits":{"cpu":"4"}}}}' \ --type=merge
  
  Increase CPU
  
  The following example sets the CPU requests to 2 CPU.
  
  oc patch Informixes informix-${INSTANCE_ID}-server \ --namespace ${PROJECT_CPD_INST_OPERANDS} \ --patch '{"spec":{"resources":{"requests":{"cpu":"2"}}}}' \ --type=merge
5. Run the following command to delete the StatefulSet for the changes to take effect:
```
oc delete sts informix-${INSTANCE_ID}-server
```
MANTA Automated Data Lineage
1. Set the SCALE environment variable to the appropriate level for your environment.
```
export SCALE=<level>
```
2. Run the following command to scale the component by updating the custom resource:
```
cpd-cli manage apply-scale-config \
--cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \
--components=mantaflow \
--scale=${SCALE}
```
OpenPages

When you provision an OpenPages service instance, you choose a size for the instance. You can also scale the OpenPages service instance.
1. Create a <filename>.yml file under the cpd-cli workspace. Configure and add the following contents to override the default custom resource name:
```
override_components_meta:
    openpages_instance:
        cr_name: <your-custom-resource-name>
```
2. Set the SCALE environment variable to the appropriate level for your environment.
```
export SCALE=<level>
```
3. Run the following command to scale the OpenPages service instance.
```
cpd-cli manage apply-scale-config \
--cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \
--components=openpages_instance \
--scale=${SCALE} \
--param-file=/tmp/work/<filename>.yml
```
Note: If the OpenPages service instance is installed in a tethered project, add the following parameter to the command.
```
--tethered_instance_ns=${PROJECT_CPD_INSTANCE_TETHERED}
```
For more information and options for scaling OpenPages, see Scaling options for OpenPages instances.
Orchestration Pipelines
1. Set the SCALE environment variable to the appropriate level for your environment.
```
export SCALE=<level>
```
2. Run the following command to scale the component by updating the custom resource:
```
cpd-cli manage apply-scale-config \
--cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \
--components=ws_pipelines \
--scale=${SCALE}
```
Planning Analytics

When you provision a Planning Analytics service instance, you choose a size for the instance.

Planning Analytics uses the command to scale the service.
1. Set the SIZE environment variable to the appropriate value for your environment.
```
export SIZE=<size>
```
  The following sizes are supported:
  
  small_mincpureq
  Use this setting when you want to use minimal reserved CPU resources without removing the CPU pod setting.
  
  small (default)
  
  medium
  
  large
2. Set the INSTANCE_NAME environment variable to the appropriate value for your environment.
```
export INSTANCE_NAME=<instance-name>
```
3. Run the following command to scale the component by updating the custom resource:
```
oc patch PAServiceInstance ${INSTANCE_NAME} \
--namespace ${PROJECT_CPD_INST_OPERANDS} \
--patch '{"spec":{"scaleConfig":"'${SIZE}'"}}' \
--type=merge
```
For more information about scaling a service instance, see Provisioning the Planning Analytics service.
Product Master
When you provision a Product Master service instance, you choose a size for the instance.
1. Set the SCALE environment variable to the appropriate level for your environment.
  export SCALE=<level>
2. Run the following command to scale the component by updating the custom resource:
  cpd-cli manage apply-scale-config \ --cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \ --components=productmaster \ --scale=${SCALE}
For more information about scaling a service instance, see Scaling Product Master instances.
Scheduling service
1. Set the SCALE environment variable to the appropriate level for your environment.
```
export SCALE=<level>
```
2. Run the following command to scale the component by updating the custom resource:
```
cpd-cli manage apply-cluster-component-scale-config \
--cluster_component_ns=${PROJECT_SCHEDULING_SERVICE} \
--component=scheduler \
--scale=${SCALE} \
--release=${VERSION}
```
SPSS Modeler

Tip: If you scale SPSS Modeler, you must also scale the Canvas component.
1. Set the SCALE environment variable to the appropriate level for your environment.
```
export SCALE=<level>
```
2. Run the following command to scale the component by updating the custom resource:
```
cpd-cli manage apply-scale-config \
--cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \
--components=spss \
--scale=${SCALE}
```
Voice Gateway

You can scale Voice Gateway by changing the number of replicas.
1. Get the list of Voice Gateway instances in the ${PROJECT_CPD_INST_OPERANDS} project:
```
oc get voicegateway --namespace ${PROJECT_CPD_INST_OPERANDS}
```
2. Set the INSTANCE_NAME environment variable to the instance of Voice Gateway that you want to scale:
```
export INSTANCE_NAME=<instance-name>
```
3. Get the current number of replicas for the instance:
```
oc get voicegateway ${INSTANCE_NAME} \
--namespace ${PROJECT_CPD_INST_OPERANDS} \
-o=jsonpath='{..status.replicas}'
```
  Use the output of this command to determine the appropriate number of replicas for the instance.
4. Set the REPLICAS environment variable to the number of replicas to use for the instance:
```
export REPLICAS=<number-of-replicas>
```
5. Scale the instance:
```
oc scale voicegateway ${INSTANCE_NAME} \
--namespace ${PROJECT_CPD_INST_OPERANDS} \
--replicas=${REPLICAS}
```
Watson Discovery

Best practice Backup your Watson Discovery installation before you scale up. In the event of an unrecoverable failure, you can use the backup to recover your existing installation. For more information, see Backing up and restoring data in Cloud Pak for Data

To scale the Elasticsearch cluster, you must update the index configuration settings before manually scaling the component. For more information about scaling the Elasticsearch cluster, see Scaling Watson Discovery.
1. Set the SCALE environment variable to the appropriate level for your environment.
```
export SCALE=<level>
```
2. Run the following command to scale the component by updating the custom resource:
```
cpd-cli manage apply-scale-config \
--cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \
--components=watson_discovery \
--scale=${SCALE}
```
Alternatively, you can scale Watson Discovery by editing the custom resource. For more information, see Scaling Watson Discovery.
Watson Machine Learning
1. Set the SCALE environment variable to the appropriate level for your environment.
```
export SCALE=<level>
```
2. Run the following command to scale the component by updating the custom resource:
```
cpd-cli manage apply-scale-config \
--cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \
--components=wml \
--scale=${SCALE}
```
Watson OpenScale
1. Set the SCALE environment variable to the appropriate level for your environment.
```
export SCALE=<level>
```
2. Run the following command to scale the component by updating the custom resource:
```
cpd-cli manage apply-scale-config \
--cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \
--components=openscale \
--scale=${SCALE}
```
Watson Speech services
1. Set the SIZE environment variable to the appropriate value for your environment.
```
export SCALE=<level>
```
  The following sizes are supported:
  
  xsmall (default)
  
  small_mincpureq
  Use this setting when you want to use minimal reserved CPU resources without removing the CPU pod setting.
  
  small
  
  medium
  
  large
2. Run the following command to scale the component by updating the custom resource.
  For Watson Speech to Text:
```
cpd-cli manage update-cr \
--component=watson_speech \
--cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \
--patch="{\"scaleConfig\":{\"stt\":{\"size\":\"${SIZE}\"}}}"
```
  For Watson Text to Speech:
```
cpd-cli manage update-cr \
--component=watson_speech \
--cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \
--patch="{\"scaleConfig\":{\"tts\":{\"size\":\"${SIZE}\"}}}"
```
Note: For detailed information about how to scale Watson Speech to Text and Watson Text to Speech, see Scaling up your Watson Speech services installation.
Watson Studio
1. Set the SCALE environment variable to the appropriate level for your environment.
```
export SCALE=<level>
```
2. Run the following command to scale the component by updating the custom resource:
```
cpd-cli manage apply-scale-config \
--cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \
--components=ws \
--scale=${SCALE}
```
Watson Studio Runtimes

Watson Studio Runtimes are started with the requested resources. You cannot scale up the started runtime. Every runtime is user and project bound.
watsonx.ai
1. Set the SCALE environment variable to the appropriate level for your environment.
```
export SCALE=<level>
```
2. Run the following command to scale the component by updating the custom resource:
```
cpd-cli manage apply-scale-config \
--cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \
--components=watsonx_ai \
--scale=${SCALE}
```
watsonx Assistant
1. Set the SCALE environment variable to the appropriate level for your environment.
```
export SCALE=<level>
```
2. Run the following command to scale the component by updating the custom resource:
```
cpd-cli manage apply-scale-config \
--cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \
--components=watson_assistant \
--scale=${SCALE}
```
watsonx Code Assistant
1. Set the SCALE environment variable to the appropriate level for your environment.
```
export SCALE=<level>
```
2. Run the following command to scale the component by updating the custom resource:
```
cpd-cli manage apply-scale-config \
--cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \
--components=wca \
--scale=${SCALE}
```
watsonx Code Assistant for Red Hat Ansible Lightspeed
1. Set the SCALE environment variable to the appropriate level for your environment.
```
export SCALE=<level>
```
2. Run the following command to scale the component by updating the custom resource:
```
cpd-cli manage apply-scale-config \
--cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \
--components=wca_ansible \
--scale=${SCALE}
```
watsonx Code Assistant for Z Agentic
1. Set the SCALE environment variable to the appropriate level for your environment.
```
export SCALE=<level>
```
2. Run the following command to scale the component by updating the custom resource:
```
cpd-cli manage apply-scale-config \
--cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \
--components=wca_z_agentic \
--scale=${SCALE}
```
watsonx Code Assistant for Z Understand
1. Set the SCALE environment variable to the appropriate level for your environment.
```
export SCALE=<level>
```
2. Run the following command to scale the component by updating the custom resource:
```
cpd-cli manage apply-scale-config \
--cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \
--components=wca_z_understand \
--scale=${SCALE}
```
watsonx.data
1. Set the SCALE environment variable to the appropriate level for your environment.
```
export SCALE=<level>
```
2. Run the following command to scale the component by updating the custom resource:
```
cpd-cli manage apply-scale-config \
--cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \
--components=watsonx_data \
--scale=${SCALE}
```
watsonx.data integration tools
The watsonx.data integration service does not support manual scaling, but the following tools support manual scaling:
- Data Observability
- Data Replication
- DataStage
1. Set the SCALE environment variable to the appropriate level for your environment.
```
export SCALE=<level>
```
2. Run the appropriate command to scale the tool by Run the following command to scale the component by updating the custom resource:
  Data Observability
  
  cpd-cli manage apply-scale-config \ --cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \ --components=ibm-databand \ --scale=${SCALE}
  
  Data Replication
  
  cpd-cli manage apply-scale-config \ --cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \ --components=replication \ --scale=${SCALE}
  
  DataStage Enterprise Plus
  
  cpd-cli manage apply-scale-config \ --cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \ --components=datastage_ent_plus \ --scale=${SCALE}
watsonx.data intelligence
1. Set the SCALE environment variable to the appropriate level for your environment.
```
export SCALE=<level>
```
2. Run the following command to scale the component by updating the custom resource:
```
cpd-cli manage apply-scale-config \
--cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \
--components=watsonx_dataintelligence \
--scale=${SCALE}
```
watsonx.data Premium
1. Set the SCALE environment variable to the appropriate level for your environment.
```
export SCALE=<level>
```
2. Run the following command to scale the component by updating the custom resource:
```
cpd-cli manage apply-scale-config \
--cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \
--components=watsonx_data_premium \
--scale=${SCALE}
```
watsonx.governance
1. Set the SIZE environment variable to the appropriate value for your environment.
```
export SIZE=<size>
```
  The following sizes are supported:
  
  small_mincpureq
  Use this setting when you want to use minimal reserved CPU resources without removing the CPU pod setting.
  
  small (default)
  
  medium
  
  large
  Note: If you scale up or scale down watsonx.governance, the value is passed to downstream services such as AI Factsheets and OpenPages.
2. Run the following command to scale the component by updating the custom resource:
```
cpd-cli manage update-cr \
--component=watsonx_governance \
--cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \
--patch="{\"scaleConfig\":\"${SIZE}\"}"
```
watsonx Orchestrate
1. Set the SCALE environment variable to the appropriate level for your environment.
```
export SCALE=<level>
```
2. Run the following command to scale the component by updating the custom resource:
```
cpd-cli manage apply-scale-config \
--cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \
--components=watsonx_orchestrate \
--scale=${SCALE}
```