Skip to content

W-22710322: Update HPA docs to include vCore ELA customer eligibility-kt #433

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
kevintroller wants to merge 1 commit into
base: latest
Choose a base branch
from
Open

W-22710322: Update HPA docs to include vCore ELA customer eligibility-kt #433

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 10 additions & 2 deletions cloudhub-2/modules/ROOT/pages/ch2-configure-horizontal-autoscaling.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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^].

Expand Down Expand Up @@ -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
Expand Down