---
schema_version: "1"
id: ebf3325c53beef8dbef8c286be66e8f0a09d021db51afec78fdd937b4393ff89
title: Configuring Horizontal Autoscaling (HPA) for CloudHub 2.0 Deployments
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/cloudhub-2/ch2-configure-horizontal-autoscaling.md
canonical_url: https://docs.mulesoft.com/cloudhub-2/ch2-configure-horizontal-autoscaling
source_site: docs.mulesoft.com
content_type: documentation
content_hash: ff4ae875a39ef1b62518d064b59afea4166869ca2c94508f2d0e75057584987b
description: MuleSoft Documentation Site
latest: true
---
---
product: CloudHub 2.0
---

# Configuring Horizontal Autoscaling (HPA) for CloudHub 2.0 Deployments

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

Configure CPU-based horizontal scaling for Mule applications to make them responsive to CPU usage by
automatically scaling up or down the deployment replicas as needed.

> [!NOTE] This feature is available to organizations with an Enterprise License Agreement (ELA) or
> those opted into the new pricing and packaging model. If the Horizontal Pod Autoscaling option
> isn’t visible in the Runtime Manager UI, contact your account team.

In Kubernetes, a Horizontal Pod Autoscaler (HPA) automatically updates a workload resource to scale
the workload to match demand. Horizontal scaling automatically deploys more pods as a response to an
increased load. For more information, visit the
[Kubernetes documentaton](https://kubernetes.io/docs/concepts/workloads/autoscaling/horizontal-pod-autoscale/).

The [Global Resource Pool Limit](https://docs.mulesoft.com/general/pricing#global-resource-pool-limits) does not limit the
applications configured with Horizontal Pod Autoscaling.

## Configure Horizontal Pod Autoscaling

To configure horizontal autoscaling for Mule apps deployed to CloudHub 2.0, follow these steps:

1.  From Anypoint Platform, select **Runtime Manager** > **Applications**.

2.  Click **Deploy application**.

3.  In the **Runtime** tab, check the **Enable CPU Based Horizontal Autoscaling** box.

4.  Set the minimum and maximum **Replica Count** limits.

    You can deploy your application with up to 8 replicas, or you can deploy with up to 16 replicas
    if you have the Anypoint Integration Advanced package or a Platinum or Titanium subscription to
    Anypoint Platform.

5.  Select the **Replica Size** from the dropdown menu.

    If you have the Anypoint Integration Advanced package, you can select from `Micro`, `Micro.Mem`,
    and `Small` replica sizes. If you have a different pricing plan, select `Micro` or `Micro.Mem`
    replica sizes. For more information, see
    [CloudHub 2.0 Application Deployment](https://docs.mulesoft.com/general/pricing#cloudhub-2-0-application-deployment).

6.  Click **Deploy Application**.

![Configure horizontal autoscaling](/mulesoft/current/en-us/cloudhub-2/_images/ch2-config-autoscaling.png)

## Autoscaling Status and Logs

When an autoscaling event occurs and your Mule application with horizontal autoscaling scales up,
you can check the **Scaling** status by clicking **View status** in your application’s details
window. You can also see your application’s **Scaling** status in the **Applications** list.

![Check the application’s scaling status.](/mulesoft/current/en-us/cloudhub-2/_images/ch2-status-autoscaling.png)

To track the scaled-up replicas startup and the number of replicas your application scaled from and
to, check the application’s logs:

1.  From Anypoint Platform, select **Runtime Manager** > **Applications**.

2.  Click the row of the application with autoscaling.

3.  Click **Manage application**.

4.  Select the **Logs** tab.

Example application log

```console
Info	8 minutes ago - 2023-11-08 14:35:01.466 PST - Runtime Manager
Application id:<app-ID> scaled UP from 1 to 2 replicas.
Info	a minute ago - 2023-11-08 14:41:24.819 PST - Runtime Manager
Application id:<app-ID> scaled DOWN from 2 to 1 replicas. :
```

You can track autoscaling events through [Audit Logs](https://docs.mulesoft.com/access-management/audit-logging) in Access
Management. Each time an application deployment scales, an audit log is published under the product
**Runtime Manager**, by user **Anypoint Staff**. The log has **Action** set to `Scaling`, and the
**Object** is the application ID.

The following is an example log payload:

```console
{"properties":{"organizationId":"my-orgID-abc","environmentId":"my-envID-xyz","response":{"message":{"message":"Application id:my-appID-123 scaled DOWN from 3 to 2 replicas.","logLevel":"INFO","context":{"logger":"Runtime Manager"},"timestamp":1700234556678}},"deploymentId":"my-appID-123","initialRequest":"/organizations/my-orgID-abc/environments/my-envID-xyz/deployments/my-appID-123/specs/my-specID-456"},"subaction":"Scaling"}
```

## Understand CPU-Based Autoscaling Policy

MuleSoft owns and applies the
[autoscaling](https://kubernetes.io/docs/concepts/workloads/autoscaling/horizontal-pod-autoscale//)
policy for your Mule application deployments.

The CPU-based HPA policy used for all Mule apps deployed to CloudHub 2.0 is as follows:

apiVersion: autoscaling/v2 kind: HorizontalPodAutoscaler metadata: name: my-app namespace:
app-namespace spec: behavior: scaleDown: policies: - periodSeconds: 15 type: Percent value: 100
selectPolicy: Max stabilizationWindowSeconds: 1800 scaleUp: policies: - periodSeconds: 180 type:
Percent value: 100 selectPolicy: Max stabilizationWindowSeconds: 0 maxReplicas: 3 metrics:

- resource: name: cpu target: averageUtilization: 70 type: Utilization type: Resource minReplicas: 1
  scaleTargetRef: apiVersion: apps/v1 kind: Deployment name: my-app

Some points to consider:

- Scale-up can occur, at most, every 180 seconds. Horizontal autoscaling might add up to 100% of the
  currently running replicas until reaching the maximum configured replicas. There is no
  stabilization window for scaling up. The target scales up immediately after the metrics indicate a
  scale-up is needed.

- Scale-down can occur, at most, every 15 seconds. Horizontal autoscaling might remove up to 100% of
  the currently running replicas, scaling down the target to the minimum allowed replicas. The
  number of replicas removed is based on the aggregated calculations over the past 1800 seconds of
  the stabilization window.

Min replicas:

- The minimum number of replicas guaranteed to run at any given moment.

- Scale-down policy should never remove replicas below this number.

Max replicas:

- The maximum number of capped replicas. No more replicas can be added above this number for scaling
  up.

- Scale-up policy should never add replicas above this number.

Enabling HPA can result in customers incurring additional flow usage when your application scales
horizontally. To avoid overages from unpredicted scaling, configure the maximum configured replicas
judiciously to stay within purchased flow limits. Track your incurred flow usage through
[usage reports](https://docs.mulesoft.com/general/usage-reports).

## Performance Considerations

For a successful horizontal autoscaling of your Mule apps, review the following performance
considerations:

- Mule apps that scale based on CPU usage are a good fit for CPU-based HPA. For example:

  - HTTP/HTTPS applications with async requests.

  - Reverse Proxies.

  - Applications with low latency and high throughput.

  - DataWeave Transformations.

  - APIKit Routing.

  - API Gateways with policies.

- Non-reentrant applications that don’t have built-in parallel processing such as batch jobs,
  scheduler applications without re-entrance and duplicate scheduling across applications, and
  applications with low throughput and high latency with large requests are not a good fit for
  CPU-based HPA.