From f3101ee9fa010524ab3a1479c1833ad2e0e6c518 Mon Sep 17 00:00:00 2001 From: Maciej Szulik Date: Tue, 15 Jun 2021 10:45:58 +0200 Subject: [PATCH] Update CronJob concept description --- .../en/docs/concepts/workloads/controllers/cron-jobs.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/content/en/docs/concepts/workloads/controllers/cron-jobs.md b/content/en/docs/concepts/workloads/controllers/cron-jobs.md index 7127924411..b441bdcd41 100644 --- a/content/en/docs/concepts/workloads/controllers/cron-jobs.md +++ b/content/en/docs/concepts/workloads/controllers/cron-jobs.md @@ -36,9 +36,10 @@ maximum length of a Job name is no more than 63 characters. ## CronJob -CronJobs are useful for creating periodic and recurring tasks, like running backups or -sending emails. CronJobs can also schedule individual tasks for a specific time, such as -scheduling a Job for when your cluster is likely to be idle. +CronJobs are meant for performing regular scheduled actions such as backups, +report generation, and so on. Each of those tasks should be configured to recur +indefinitely (for example: once a day / week / month); you can define the point +in time within that interval when the job should start. ### Example