uucas.blogg.se - Prometheus cpu usage

This specification describes the cpu trigger that scales based on cpu metrics. # a working example of resources with specified limits If the resources section is empty ( resources: occurs. See Resource Management for Pods and Containers. The configuration for your Kubernetes Pods must include a resources section with specified limits.Installation instructions vary based on your Kubernetes provider.

The Kubernetes Metrics Server must be installed.

Additionally, the resources section of the relevant Kubernetes Pods must include limits (at a minimum). KEDA uses standard cpu and memory metrics from the Kubernetes Metrics Server, which is not installed by default on certain Kubernetes deployments such as EKS on AWS.

This scaler only applies to ScaledObject, not to Scaling Jobs.

Kafka + cpu/memory, or Prometheus + cpu/memory), the deployment will never scale to 0. This scaler will never scale to 0 and even when user defines multiple scaler types (eg.