From eb3f374d374b91d2c2e1f33271f5f49b6be3c620 Mon Sep 17 00:00:00 2001 From: Jorge Bianquetti Date: Tue, 20 Jun 2017 19:33:22 +0200 Subject: [PATCH] info about cron jobs updated (#4110) --- docs/concepts/workloads/controllers/cron-jobs.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/concepts/workloads/controllers/cron-jobs.md b/docs/concepts/workloads/controllers/cron-jobs.md index 51341cdcaa..e823dfb09a 100644 --- a/docs/concepts/workloads/controllers/cron-jobs.md +++ b/docs/concepts/workloads/controllers/cron-jobs.md @@ -40,7 +40,9 @@ A typical use case is: You need a working Kubernetes cluster at version >= 1.4 (for ScheduledJob), >= 1.5 (for CronJob), with batch/v2alpha1 API turned on by passing `--runtime-config=batch/v2alpha1=true` while bringing up the API server (see [Turn on or off an API version for your cluster](/docs/admin/cluster-management/#turn-on-or-off-an-api-version-for-your-cluster) -for more). You cannot use Cron Jobs on a hosted Kubernetes provider that has disabled alpha resources. +for more). + +Beginning with 1.6 series Cron Jobs are enabled by default, but note that you can not use Cron Jobs on a hosted Kubernetes provider that has disabled alpha resources. ## Creating a Cron Job