In the ACM 2.11 documentation, it mentions that a user can scale the machinepool using the provided commands. However, in this hub cluster, there are two Custom Resource Definitions (CRDs) for machinepools: machinepools.cluster.x-k8s.io (upstream CAPI) and machinepools.hive.openshift.io.  Due to the co-existence of multiple machinepool CRDs, the upstream Cluster API (CAPI) CRD takes priority. 

To scale a node successfully, users must specify the full CRD name to differentiate between the two machinepool CRDs. Please address this discrepancy in the documentation

machinepools.cluster.x-k8s.io                                             2024-11-01T20:47:02Z
machinepools.hive.openshift.io                                            2024-11-01T20:45:05Z

$oc get machinepools -A
No resources found

$oc get machinepools.hive.openshift.io -A
NAMESPACE      NAME                  POOLNAME   CLUSTERDEPLOYMENT   REPLICAS
dchong-spoke   dchong-spoke-worker   worker     dchong-spoke        3

$oc get machinepools dchong-spoke -v 6
I1104 11:06:01.107727    7222 loader.go:373] Config loaded from file:  /home/daniel/OpenShift/installer-4.17/SNO/auth/kubeconfig
I1104 11:06:01.256144    7222 round_trippers.go:553] GET https://api.dchong-sno.nasa.aws.cee.support:6443/apis/cluster.x-k8s.io/v1beta1/namespaces/hive/machinepools/dchong-spoke 404 Not Found in 139 milliseconds

[documentation location]:

https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.11/html/clusters/cluster_mce_overview#manual-cli