From bfe06a2686a1d6e4616f50d3a87f66bf32194441 Mon Sep 17 00:00:00 2001 From: solsson Date: Mon, 6 Dec 2021 11:52:57 +0100 Subject: [PATCH] The kubernetes-workload scaler should only count running pods (#605) Signed-off-by: Staffan Olsson --- content/docs/2.6/scalers/kubernetes-workload.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/content/docs/2.6/scalers/kubernetes-workload.md b/content/docs/2.6/scalers/kubernetes-workload.md index bcc0e557f42..1d4e38c5dc7 100644 --- a/content/docs/2.6/scalers/kubernetes-workload.md +++ b/content/docs/2.6/scalers/kubernetes-workload.md @@ -3,7 +3,7 @@ title = "Kubernetes Workload" layout = "scaler" availability = "v2.4+" maintainer = "Community" -description = "Scale applications based on the amount of pods which matches the given selectors." +description = "Scale applications based on the count of running pods that match the given selectors." go_file = "kubernetes_workload_scaler" +++ @@ -24,6 +24,8 @@ triggers: > 💡 **Note:** The search scope is limited to the namespace where the `ScaledObject` is deployed. +The count excludes terminated pods, i.e. [pod status](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.22/#podstatus-v1-core) `phase` equals `Succeeded` or `Failed`. + ### Authentication Parameters The own KEDA's identity is used to list the pods, so no extra configuration is needed here.