After scaling a Process Mining deployment, which two replica set values are updated?

When scaling an IBM Process Mining deployment, which runs on a container orchestration platform like Red Hat OpenShift, the administrator modifies the Custom Resource (CR) to specify the target number of replicas. This action directly updates the DESIRED state in the corresponding Deployment or StatefulSet object. The platform's controller then initiates the scaling process, creating or terminating pods to match this new desired state. As these new pods start and become fully operational (passing their readiness probes), the READY count is updated to reflect the current number of available and healthy replicas.

B. PROGRESS: This is not a standard replica set value. Progressing is a condition type in a Deployment's status, indicating an update is underway, but it is not a replica count.
C. WAITING: This describes a state for a container within a pod (e.g., waiting for an image pull), not a top-level replica set count.
D. COMPLETED: This status is relevant for resources that run to completion, such as a Kubernetes Job, not for long-running service deployments that are scaled up or down.

1. IBM Cloud Pak for Business Automation Documentation: In the section on administering Process Mining

the process of scaling involves modifying the spec.replicas parameter in the custom resource file. This parameter directly corresponds to the DESIRED number of pods.

Source: IBM Documentation

"IBM Cloud Pak for Business Automation 23.0.2"

Administering

"Process Mining custom resource". The documentation details the configurable parameters

including spec.replicas for various components

which sets the desired state for the deployment.

2. Kubernetes Documentation (Foundational Technology): The official Kubernetes documentation explains the lifecycle and status of a Deployment. The .spec.replicas field is the DESIRED state. The .status.readyReplicas field is the READY state

which is updated by the system as pods become available.

Source: Kubernetes Documentation

Concepts > Workloads > Controllers > Deployments

"Deployment Status" section. It states: "readyReplicas is the number of replicas that are ready for service... The desired number of replicas is specified in .spec.replicas."