From 9711e815ed3b48bc588485b43e700f445d5bee53 Mon Sep 17 00:00:00 2001 From: Ruben Laguna Date: Thu, 7 Mar 2024 08:22:57 +0100 Subject: [PATCH] Make the example match the screenshot Signed-off-by: Ruben Laguna --- content/docs/1.5/scalers/cron.md | 12 ++++++------ content/docs/2.0/scalers/cron.md | 12 ++++++------ content/docs/2.1/scalers/cron.md | 12 ++++++------ content/docs/2.10/scalers/cron.md | 12 ++++++------ content/docs/2.11/scalers/cron.md | 12 ++++++------ content/docs/2.12/scalers/cron.md | 12 ++++++------ content/docs/2.13/scalers/cron.md | 12 ++++++------ content/docs/2.14/scalers/cron.md | 12 ++++++------ content/docs/2.2/scalers/cron.md | 12 ++++++------ content/docs/2.3/scalers/cron.md | 12 ++++++------ content/docs/2.4/scalers/cron.md | 12 ++++++------ content/docs/2.5/scalers/cron.md | 12 ++++++------ content/docs/2.6/scalers/cron.md | 12 ++++++------ content/docs/2.7/scalers/cron.md | 12 ++++++------ content/docs/2.8/scalers/cron.md | 12 ++++++------ content/docs/2.9/scalers/cron.md | 12 ++++++------ 16 files changed, 96 insertions(+), 96 deletions(-) diff --git a/content/docs/1.5/scalers/cron.md b/content/docs/1.5/scalers/cron.md index 38f256624..9e064336b 100644 --- a/content/docs/1.5/scalers/cron.md +++ b/content/docs/1.5/scalers/cron.md @@ -16,8 +16,8 @@ triggers: metadata: # Required timezone: Asia/Kolkata # The acceptable values would be a value from the IANA Time Zone Database. - start: 30 * * * * # Every hour on the 30th minute - end: 45 * * * * # Every hour on the 45th minute + start: 0 6 * * * # At 6:00 AM + end: 0 20 * * * # At 8:00 PM desiredReplicas: "10" ``` @@ -33,8 +33,8 @@ triggers: > > For example, the following schedule is not valid: > ```yaml -> start: 30 * * * * -> end: 30 * * * * +> start: 0 6 * * * # At 6:00 AM +> end: 0 6 * * * # also at 6:00 AM >``` ### How does it work? @@ -62,7 +62,7 @@ spec: - type: cron metadata: timezone: Asia/Kolkata - start: 30 * * * * - end: 45 * * * * + start: 0 6 * * * + end: 0 20 * * * desiredReplicas: "10" ``` diff --git a/content/docs/2.0/scalers/cron.md b/content/docs/2.0/scalers/cron.md index 9822af10d..34531d452 100644 --- a/content/docs/2.0/scalers/cron.md +++ b/content/docs/2.0/scalers/cron.md @@ -16,8 +16,8 @@ triggers: metadata: # Required timezone: Asia/Kolkata # The acceptable values would be a value from the IANA Time Zone Database. - start: 30 * * * * # Every hour on the 30th minute - end: 45 * * * * # Every hour on the 45th minute + start: 0 6 * * * # At 6:00 AM + end: 0 20 * * * # At 8:00 PM desiredReplicas: "10" ``` @@ -33,8 +33,8 @@ triggers: > > For example, the following schedule is not valid: > ```yaml -> start: 30 * * * * -> end: 30 * * * * +> start: 0 6 * * * # At 6:00 AM +> end: 0 6 * * * # also at 6:00 AM >``` ### How does it work? @@ -62,7 +62,7 @@ spec: - type: cron metadata: timezone: Asia/Kolkata - start: 30 * * * * - end: 45 * * * * + start: 0 6 * * * + end: 0 20 * * * desiredReplicas: "10" ``` diff --git a/content/docs/2.1/scalers/cron.md b/content/docs/2.1/scalers/cron.md index 9822af10d..34531d452 100644 --- a/content/docs/2.1/scalers/cron.md +++ b/content/docs/2.1/scalers/cron.md @@ -16,8 +16,8 @@ triggers: metadata: # Required timezone: Asia/Kolkata # The acceptable values would be a value from the IANA Time Zone Database. - start: 30 * * * * # Every hour on the 30th minute - end: 45 * * * * # Every hour on the 45th minute + start: 0 6 * * * # At 6:00 AM + end: 0 20 * * * # At 8:00 PM desiredReplicas: "10" ``` @@ -33,8 +33,8 @@ triggers: > > For example, the following schedule is not valid: > ```yaml -> start: 30 * * * * -> end: 30 * * * * +> start: 0 6 * * * # At 6:00 AM +> end: 0 6 * * * # also at 6:00 AM >``` ### How does it work? @@ -62,7 +62,7 @@ spec: - type: cron metadata: timezone: Asia/Kolkata - start: 30 * * * * - end: 45 * * * * + start: 0 6 * * * + end: 0 20 * * * desiredReplicas: "10" ``` diff --git a/content/docs/2.10/scalers/cron.md b/content/docs/2.10/scalers/cron.md index 80cf3a5a8..daaf3055d 100644 --- a/content/docs/2.10/scalers/cron.md +++ b/content/docs/2.10/scalers/cron.md @@ -16,8 +16,8 @@ triggers: metadata: # Required timezone: Asia/Kolkata # The acceptable values would be a value from the IANA Time Zone Database. - start: 30 * * * * # Every hour on the 30th minute - end: 45 * * * * # Every hour on the 45th minute + start: 0 6 * * * # At 6:00 AM + end: 0 20 * * * # At 8:00 PM desiredReplicas: "10" ``` @@ -35,8 +35,8 @@ triggers: > > For example, the following schedule is not valid: > ```yaml -> start: 30 * * * * -> end: 30 * * * * +> start: 0 6 * * * # At 6:00 AM +> end: 0 6 * * * # also at 6:00 AM >``` ### How does it work? @@ -64,7 +64,7 @@ spec: - type: cron metadata: timezone: Asia/Kolkata - start: 30 * * * * - end: 45 * * * * + start: 0 6 * * * + end: 0 20 * * * desiredReplicas: "10" ``` diff --git a/content/docs/2.11/scalers/cron.md b/content/docs/2.11/scalers/cron.md index 80cf3a5a8..daaf3055d 100644 --- a/content/docs/2.11/scalers/cron.md +++ b/content/docs/2.11/scalers/cron.md @@ -16,8 +16,8 @@ triggers: metadata: # Required timezone: Asia/Kolkata # The acceptable values would be a value from the IANA Time Zone Database. - start: 30 * * * * # Every hour on the 30th minute - end: 45 * * * * # Every hour on the 45th minute + start: 0 6 * * * # At 6:00 AM + end: 0 20 * * * # At 8:00 PM desiredReplicas: "10" ``` @@ -35,8 +35,8 @@ triggers: > > For example, the following schedule is not valid: > ```yaml -> start: 30 * * * * -> end: 30 * * * * +> start: 0 6 * * * # At 6:00 AM +> end: 0 6 * * * # also at 6:00 AM >``` ### How does it work? @@ -64,7 +64,7 @@ spec: - type: cron metadata: timezone: Asia/Kolkata - start: 30 * * * * - end: 45 * * * * + start: 0 6 * * * + end: 0 20 * * * desiredReplicas: "10" ``` diff --git a/content/docs/2.12/scalers/cron.md b/content/docs/2.12/scalers/cron.md index 80cf3a5a8..daaf3055d 100644 --- a/content/docs/2.12/scalers/cron.md +++ b/content/docs/2.12/scalers/cron.md @@ -16,8 +16,8 @@ triggers: metadata: # Required timezone: Asia/Kolkata # The acceptable values would be a value from the IANA Time Zone Database. - start: 30 * * * * # Every hour on the 30th minute - end: 45 * * * * # Every hour on the 45th minute + start: 0 6 * * * # At 6:00 AM + end: 0 20 * * * # At 8:00 PM desiredReplicas: "10" ``` @@ -35,8 +35,8 @@ triggers: > > For example, the following schedule is not valid: > ```yaml -> start: 30 * * * * -> end: 30 * * * * +> start: 0 6 * * * # At 6:00 AM +> end: 0 6 * * * # also at 6:00 AM >``` ### How does it work? @@ -64,7 +64,7 @@ spec: - type: cron metadata: timezone: Asia/Kolkata - start: 30 * * * * - end: 45 * * * * + start: 0 6 * * * + end: 0 20 * * * desiredReplicas: "10" ``` diff --git a/content/docs/2.13/scalers/cron.md b/content/docs/2.13/scalers/cron.md index 80cf3a5a8..daaf3055d 100644 --- a/content/docs/2.13/scalers/cron.md +++ b/content/docs/2.13/scalers/cron.md @@ -16,8 +16,8 @@ triggers: metadata: # Required timezone: Asia/Kolkata # The acceptable values would be a value from the IANA Time Zone Database. - start: 30 * * * * # Every hour on the 30th minute - end: 45 * * * * # Every hour on the 45th minute + start: 0 6 * * * # At 6:00 AM + end: 0 20 * * * # At 8:00 PM desiredReplicas: "10" ``` @@ -35,8 +35,8 @@ triggers: > > For example, the following schedule is not valid: > ```yaml -> start: 30 * * * * -> end: 30 * * * * +> start: 0 6 * * * # At 6:00 AM +> end: 0 6 * * * # also at 6:00 AM >``` ### How does it work? @@ -64,7 +64,7 @@ spec: - type: cron metadata: timezone: Asia/Kolkata - start: 30 * * * * - end: 45 * * * * + start: 0 6 * * * + end: 0 20 * * * desiredReplicas: "10" ``` diff --git a/content/docs/2.14/scalers/cron.md b/content/docs/2.14/scalers/cron.md index 80cf3a5a8..daaf3055d 100644 --- a/content/docs/2.14/scalers/cron.md +++ b/content/docs/2.14/scalers/cron.md @@ -16,8 +16,8 @@ triggers: metadata: # Required timezone: Asia/Kolkata # The acceptable values would be a value from the IANA Time Zone Database. - start: 30 * * * * # Every hour on the 30th minute - end: 45 * * * * # Every hour on the 45th minute + start: 0 6 * * * # At 6:00 AM + end: 0 20 * * * # At 8:00 PM desiredReplicas: "10" ``` @@ -35,8 +35,8 @@ triggers: > > For example, the following schedule is not valid: > ```yaml -> start: 30 * * * * -> end: 30 * * * * +> start: 0 6 * * * # At 6:00 AM +> end: 0 6 * * * # also at 6:00 AM >``` ### How does it work? @@ -64,7 +64,7 @@ spec: - type: cron metadata: timezone: Asia/Kolkata - start: 30 * * * * - end: 45 * * * * + start: 0 6 * * * + end: 0 20 * * * desiredReplicas: "10" ``` diff --git a/content/docs/2.2/scalers/cron.md b/content/docs/2.2/scalers/cron.md index 9822af10d..34531d452 100644 --- a/content/docs/2.2/scalers/cron.md +++ b/content/docs/2.2/scalers/cron.md @@ -16,8 +16,8 @@ triggers: metadata: # Required timezone: Asia/Kolkata # The acceptable values would be a value from the IANA Time Zone Database. - start: 30 * * * * # Every hour on the 30th minute - end: 45 * * * * # Every hour on the 45th minute + start: 0 6 * * * # At 6:00 AM + end: 0 20 * * * # At 8:00 PM desiredReplicas: "10" ``` @@ -33,8 +33,8 @@ triggers: > > For example, the following schedule is not valid: > ```yaml -> start: 30 * * * * -> end: 30 * * * * +> start: 0 6 * * * # At 6:00 AM +> end: 0 6 * * * # also at 6:00 AM >``` ### How does it work? @@ -62,7 +62,7 @@ spec: - type: cron metadata: timezone: Asia/Kolkata - start: 30 * * * * - end: 45 * * * * + start: 0 6 * * * + end: 0 20 * * * desiredReplicas: "10" ``` diff --git a/content/docs/2.3/scalers/cron.md b/content/docs/2.3/scalers/cron.md index 9822af10d..34531d452 100644 --- a/content/docs/2.3/scalers/cron.md +++ b/content/docs/2.3/scalers/cron.md @@ -16,8 +16,8 @@ triggers: metadata: # Required timezone: Asia/Kolkata # The acceptable values would be a value from the IANA Time Zone Database. - start: 30 * * * * # Every hour on the 30th minute - end: 45 * * * * # Every hour on the 45th minute + start: 0 6 * * * # At 6:00 AM + end: 0 20 * * * # At 8:00 PM desiredReplicas: "10" ``` @@ -33,8 +33,8 @@ triggers: > > For example, the following schedule is not valid: > ```yaml -> start: 30 * * * * -> end: 30 * * * * +> start: 0 6 * * * # At 6:00 AM +> end: 0 6 * * * # also at 6:00 AM >``` ### How does it work? @@ -62,7 +62,7 @@ spec: - type: cron metadata: timezone: Asia/Kolkata - start: 30 * * * * - end: 45 * * * * + start: 0 6 * * * + end: 0 20 * * * desiredReplicas: "10" ``` diff --git a/content/docs/2.4/scalers/cron.md b/content/docs/2.4/scalers/cron.md index 9822af10d..34531d452 100644 --- a/content/docs/2.4/scalers/cron.md +++ b/content/docs/2.4/scalers/cron.md @@ -16,8 +16,8 @@ triggers: metadata: # Required timezone: Asia/Kolkata # The acceptable values would be a value from the IANA Time Zone Database. - start: 30 * * * * # Every hour on the 30th minute - end: 45 * * * * # Every hour on the 45th minute + start: 0 6 * * * # At 6:00 AM + end: 0 20 * * * # At 8:00 PM desiredReplicas: "10" ``` @@ -33,8 +33,8 @@ triggers: > > For example, the following schedule is not valid: > ```yaml -> start: 30 * * * * -> end: 30 * * * * +> start: 0 6 * * * # At 6:00 AM +> end: 0 6 * * * # also at 6:00 AM >``` ### How does it work? @@ -62,7 +62,7 @@ spec: - type: cron metadata: timezone: Asia/Kolkata - start: 30 * * * * - end: 45 * * * * + start: 0 6 * * * + end: 0 20 * * * desiredReplicas: "10" ``` diff --git a/content/docs/2.5/scalers/cron.md b/content/docs/2.5/scalers/cron.md index 80cf3a5a8..daaf3055d 100644 --- a/content/docs/2.5/scalers/cron.md +++ b/content/docs/2.5/scalers/cron.md @@ -16,8 +16,8 @@ triggers: metadata: # Required timezone: Asia/Kolkata # The acceptable values would be a value from the IANA Time Zone Database. - start: 30 * * * * # Every hour on the 30th minute - end: 45 * * * * # Every hour on the 45th minute + start: 0 6 * * * # At 6:00 AM + end: 0 20 * * * # At 8:00 PM desiredReplicas: "10" ``` @@ -35,8 +35,8 @@ triggers: > > For example, the following schedule is not valid: > ```yaml -> start: 30 * * * * -> end: 30 * * * * +> start: 0 6 * * * # At 6:00 AM +> end: 0 6 * * * # also at 6:00 AM >``` ### How does it work? @@ -64,7 +64,7 @@ spec: - type: cron metadata: timezone: Asia/Kolkata - start: 30 * * * * - end: 45 * * * * + start: 0 6 * * * + end: 0 20 * * * desiredReplicas: "10" ``` diff --git a/content/docs/2.6/scalers/cron.md b/content/docs/2.6/scalers/cron.md index 80cf3a5a8..daaf3055d 100644 --- a/content/docs/2.6/scalers/cron.md +++ b/content/docs/2.6/scalers/cron.md @@ -16,8 +16,8 @@ triggers: metadata: # Required timezone: Asia/Kolkata # The acceptable values would be a value from the IANA Time Zone Database. - start: 30 * * * * # Every hour on the 30th minute - end: 45 * * * * # Every hour on the 45th minute + start: 0 6 * * * # At 6:00 AM + end: 0 20 * * * # At 8:00 PM desiredReplicas: "10" ``` @@ -35,8 +35,8 @@ triggers: > > For example, the following schedule is not valid: > ```yaml -> start: 30 * * * * -> end: 30 * * * * +> start: 0 6 * * * # At 6:00 AM +> end: 0 6 * * * # also at 6:00 AM >``` ### How does it work? @@ -64,7 +64,7 @@ spec: - type: cron metadata: timezone: Asia/Kolkata - start: 30 * * * * - end: 45 * * * * + start: 0 6 * * * + end: 0 20 * * * desiredReplicas: "10" ``` diff --git a/content/docs/2.7/scalers/cron.md b/content/docs/2.7/scalers/cron.md index 80cf3a5a8..daaf3055d 100644 --- a/content/docs/2.7/scalers/cron.md +++ b/content/docs/2.7/scalers/cron.md @@ -16,8 +16,8 @@ triggers: metadata: # Required timezone: Asia/Kolkata # The acceptable values would be a value from the IANA Time Zone Database. - start: 30 * * * * # Every hour on the 30th minute - end: 45 * * * * # Every hour on the 45th minute + start: 0 6 * * * # At 6:00 AM + end: 0 20 * * * # At 8:00 PM desiredReplicas: "10" ``` @@ -35,8 +35,8 @@ triggers: > > For example, the following schedule is not valid: > ```yaml -> start: 30 * * * * -> end: 30 * * * * +> start: 0 6 * * * # At 6:00 AM +> end: 0 6 * * * # also at 6:00 AM >``` ### How does it work? @@ -64,7 +64,7 @@ spec: - type: cron metadata: timezone: Asia/Kolkata - start: 30 * * * * - end: 45 * * * * + start: 0 6 * * * + end: 0 20 * * * desiredReplicas: "10" ``` diff --git a/content/docs/2.8/scalers/cron.md b/content/docs/2.8/scalers/cron.md index 80cf3a5a8..daaf3055d 100644 --- a/content/docs/2.8/scalers/cron.md +++ b/content/docs/2.8/scalers/cron.md @@ -16,8 +16,8 @@ triggers: metadata: # Required timezone: Asia/Kolkata # The acceptable values would be a value from the IANA Time Zone Database. - start: 30 * * * * # Every hour on the 30th minute - end: 45 * * * * # Every hour on the 45th minute + start: 0 6 * * * # At 6:00 AM + end: 0 20 * * * # At 8:00 PM desiredReplicas: "10" ``` @@ -35,8 +35,8 @@ triggers: > > For example, the following schedule is not valid: > ```yaml -> start: 30 * * * * -> end: 30 * * * * +> start: 0 6 * * * # At 6:00 AM +> end: 0 6 * * * # also at 6:00 AM >``` ### How does it work? @@ -64,7 +64,7 @@ spec: - type: cron metadata: timezone: Asia/Kolkata - start: 30 * * * * - end: 45 * * * * + start: 0 6 * * * + end: 0 20 * * * desiredReplicas: "10" ``` diff --git a/content/docs/2.9/scalers/cron.md b/content/docs/2.9/scalers/cron.md index 80cf3a5a8..daaf3055d 100644 --- a/content/docs/2.9/scalers/cron.md +++ b/content/docs/2.9/scalers/cron.md @@ -16,8 +16,8 @@ triggers: metadata: # Required timezone: Asia/Kolkata # The acceptable values would be a value from the IANA Time Zone Database. - start: 30 * * * * # Every hour on the 30th minute - end: 45 * * * * # Every hour on the 45th minute + start: 0 6 * * * # At 6:00 AM + end: 0 20 * * * # At 8:00 PM desiredReplicas: "10" ``` @@ -35,8 +35,8 @@ triggers: > > For example, the following schedule is not valid: > ```yaml -> start: 30 * * * * -> end: 30 * * * * +> start: 0 6 * * * # At 6:00 AM +> end: 0 6 * * * # also at 6:00 AM >``` ### How does it work? @@ -64,7 +64,7 @@ spec: - type: cron metadata: timezone: Asia/Kolkata - start: 30 * * * * - end: 45 * * * * + start: 0 6 * * * + end: 0 20 * * * desiredReplicas: "10" ```