From 7eef7fcad21729d6c41e23d45423404f27fa9450 Mon Sep 17 00:00:00 2001 From: Gaurav Abbi Date: Wed, 3 Jan 2024 10:33:55 +0100 Subject: [PATCH] keda-cron-scaler - Update README.md --- keda-cron-scaler/README.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/keda-cron-scaler/README.md b/keda-cron-scaler/README.md index ef647399..82cd7e03 100644 --- a/keda-cron-scaler/README.md +++ b/keda-cron-scaler/README.md @@ -28,13 +28,15 @@ As an illustration, the cron-based scaler enables you to: > **Note:** This only benefits when your workloads require more resources than the base setup. The [current base setup](https://kyma-project.github.io/price-calculator/) consists of 3 VMs, each with 4 CPU and 16 GB of RAM. Therefore, if your workloads need 4 or more VMs to be provisioned, this feature can provide benefits to control costs during off-work hours. + > **Note:** The cron scheduling is applicable to only customer workloads and **not kyma components**. + ![off-work](assets/keda-scale-off-work.png) ## Scenario Lets put cron based scaler to action. -Assume we have a **development cluster** where we want to run workloads only during work hours. +Assume we have a **development cluster** where we want to run customer workloads only during work hours. Lets say **Monday - Friday, 8 AM to 6 PM**