mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
30 lines
1.4 KiB
Plaintext
30 lines
1.4 KiB
Plaintext
:_mod-docs-content-type: ASSEMBLY
|
|
:context: nodes-cma-autoscaling-custom-adding
|
|
[id="nodes-cma-autoscaling-custom-adding"]
|
|
= Understanding how to add custom metrics autoscalers
|
|
include::_attributes/common-attributes.adoc[]
|
|
|
|
toc::[]
|
|
|
|
|
|
To add a custom metrics autoscaler, create a `ScaledObject` custom resource for a deployment, stateful set, or custom resource. Create a `ScaledJob` custom resource for a job.
|
|
|
|
You can create only one scaled object for each workload that you want to scale. Also, you cannot use a scaled object and the horizontal pod autoscaler (HPA) on the same workload.
|
|
|
|
// If you want to scale based on a custom trigger and CPU/Memory, you can create multiple triggers in the scaled object or scaled job.
|
|
|
|
include::modules/nodes-cma-autoscaling-custom-creating-workload.adoc[leveloffset=+1]
|
|
|
|
//Scaling by using a scaled job is a Technology Preview feature. TP not supported in ROSA/OSD
|
|
ifndef::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
|
|
include::modules/nodes-cma-autoscaling-custom-creating-job.adoc[leveloffset=+1]
|
|
|
|
endif::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
|
|
|
|
[role="_additional-resources"]
|
|
[id="nodes-cma-autoscaling-custom-adding-additional-resources"]
|
|
== Additional resources
|
|
|
|
* xref:../../nodes/cma/nodes-cma-autoscaling-custom-trigger-auth.adoc#nodes-cma-autoscaling-custom-trigger-auth[Understanding custom metrics autoscaler trigger authentications]
|
|
|