Skip to content

Commit

Permalink
fix: use the external link to avoid hash valitations in faq section (k…
Browse files Browse the repository at this point in the history
  • Loading branch information
Jorge Turrado Ferrero authored Jun 15, 2022
1 parent 3728b37 commit 83b96de
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion data/faq20.toml
Original file line number Diff line number Diff line change
Expand Up @@ -72,7 +72,7 @@ The target metric value is used by the Horizontal Pod Autoscaler (HPA) to make s
The current target value on the Horizontal Pod Autoscaler (HPA) often does not match with the metrics on the system you are scaling on. This is because of how the Horizontal Pod Autoscaler's (HPA) [scaling algorithm](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/#algorithm-details) works.
By default, KEDA scalers use average metrics (the `AverageValue` metric type). This means that the HPA will use the average value of the metric between the total amount of pods. As of KEDA v2.7, ScaledObjects also support the `Value` metric type. You can learn more about it [here](/docs/latest/concepts/scaling-deployments/#triggers).
By default, KEDA scalers use average metrics (the `AverageValue` metric type). This means that the HPA will use the average value of the metric between the total amount of pods. As of KEDA v2.7, ScaledObjects also support the `Value` metric type. You can learn more about it [here](https://keda.sh/docs/latest/concepts/scaling-deployments/#triggers).
"""
type = "Kubernetes"

Expand Down

0 comments on commit 83b96de

Please sign in to comment.