From 832bc77881b17ce63aa486602067a561ac635320 Mon Sep 17 00:00:00 2001
From: amirschw <24677563+amirschw@users.noreply.github.com>
Date: Thu, 9 Jun 2022 10:16:40 +0300
Subject: [PATCH] Document ScaledObject support for Value metric type in FAQ

Signed-off-by: amirschw <24677563+amirschw@users.noreply.github.com>
---
 data/faq20.toml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/data/faq20.toml b/data/faq20.toml
index a4f54af70..3371b953c 100644
--- a/data/faq20.toml
+++ b/data/faq20.toml
@@ -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.
 
-KEDA currently only supports average metrics. This means that the HPA will use the average value of the metric between the total amount of pods.
+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).
 """
 type = "Kubernetes"