:_mod-docs-content-type: ASSEMBLY
:context: nodes-cma-autoscaling-custom-trigger
[id="nodes-cma-autoscaling-custom-overview-trigger"]
= Understanding custom metrics autoscaler triggers
include::_attributes/common-attributes.adoc[]

toc::[]



Triggers, also known as scalers, provide the metrics that the Custom Metrics Autoscaler Operator uses to scale your pods.

The custom metrics autoscaler currently supports the Prometheus, CPU, memory, Apache Kafka, and cron triggers.

You use a `ScaledObject` or `ScaledJob` custom resource to configure triggers for specific objects, as described in the sections that follow.

You can configure a certificate authority xref:../../nodes/cma/nodes-cma-autoscaling-custom-trigger-auth.adoc#nodes-cma-autoscaling-custom-trigger-auth[to use with your scaled objects] or  xref:../../nodes/cma/nodes-cma-autoscaling-custom.adoc#nodes-cma-autoscaling-custom-ca_nodes-cma-autoscaling-custom[for all scalers in the cluster].

// The following include statements pull in the module files that comprise
// the assembly. Include any combination of concept, procedure, or reference
// modules required to cover the user story. You can also include other
// assemblies.

include::modules/nodes-cma-autoscaling-custom-trigger-prom.adoc[leveloffset=+1]

include::modules/nodes-cma-autoscaling-custom-trigger-prom-gpu.adoc[leveloffset=+2]

include::modules/nodes-cma-autoscaling-custom-prometheus-config.adoc[leveloffset=+2]

[role="_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]

include::modules/nodes-cma-autoscaling-custom-trigger-cpu.adoc[leveloffset=+1]

include::modules/nodes-cma-autoscaling-custom-trigger-memory.adoc[leveloffset=+1]

include::modules/nodes-cma-autoscaling-custom-trigger-kafka.adoc[leveloffset=+1]

include::modules/nodes-cma-autoscaling-custom-trigger-cron.adoc[leveloffset=+1]

include::modules/nodes-cma-autoscaling-custom-trigger-workload.adoc[leveloffset=+1]
