From 592898d23d8409d2c54c57724f53dda21126452b Mon Sep 17 00:00:00 2001 From: ktroller Date: Wed, 3 Jun 2026 13:38:42 -0300 Subject: [PATCH] W-22710322: Update HPA docs to include vCore ELA customer eligibility HPA is now available to vCore ELA customers with the Autoscaling SKU, not only to new pricing/packaging customers. Updated the eligibility note and the usage/billing guidance to distinguish vCore ELA (no overage billing, unified usage reports) from flow-based pricing customers. --- .../pages/ch2-configure-horizontal-autoscaling.adoc | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/cloudhub-2/modules/ROOT/pages/ch2-configure-horizontal-autoscaling.adoc b/cloudhub-2/modules/ROOT/pages/ch2-configure-horizontal-autoscaling.adoc index f1ae7e5d..41d35542 100644 --- a/cloudhub-2/modules/ROOT/pages/ch2-configure-horizontal-autoscaling.adoc +++ b/cloudhub-2/modules/ROOT/pages/ch2-configure-horizontal-autoscaling.adoc @@ -6,7 +6,12 @@ endif::[] 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 applies only to customers who are opted into the new pricing and packaging model. For more details, see xref:general::pricing.adoc[] +==== +This feature is available to these customers: + +* vCore ELA customers on CloudHub 2.0 with the Autoscaling SKU provisioned on their account. If the HPA option is not visible in Runtime Manager, contact your account team to confirm the SKU is enabled. +* Customers opted into the Anypoint Integration Advanced package or a Platinum or Titanium subscription. For more details, see xref:general::pricing.adoc[]. +==== 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 https://kubernetes.io/docs/concepts/workloads/autoscaling/horizontal-pod-autoscale/[Kubernetes documentaton^]. @@ -120,7 +125,10 @@ 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 xref:general::usage-reports.adoc[usage reports]. +Enabling HPA can result in additional resource consumption when your application scales horizontally. Configure the maximum number of replicas judiciously to stay within your purchased limits: + +* vCore ELA customers: HPA doesn't introduce overage billing. Your contracted vCore allotment governs your renewal. Monitor combined vCore consumption across CloudHub and CloudHub 2.0 in the unified xref:general::usage-reports.adoc[Usage Reports] dashboard. +* Flow-based pricing customers (Anypoint Integration Advanced, Platinum, or Titanium): To avoid overages from unpredicted scaling, stay within your purchased flow limits. Track your incurred flow usage through xref:general::usage-reports.adoc[usage reports]. == Performance Considerations