From 8716e152b39a16fda84b285c56a242c62cec76e5 Mon Sep 17 00:00:00 2001 From: Denis Gladkikh Date: Sun, 25 Jun 2017 06:14:44 -0700 Subject: [PATCH] CronJobs aren't enabled in 1.6 by default --- docs/concepts/workloads/controllers/cron-jobs.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/docs/concepts/workloads/controllers/cron-jobs.md b/docs/concepts/workloads/controllers/cron-jobs.md index e823dfb09a..82f9b2a078 100644 --- a/docs/concepts/workloads/controllers/cron-jobs.md +++ b/docs/concepts/workloads/controllers/cron-jobs.md @@ -42,8 +42,6 @@ with batch/v2alpha1 API turned on by passing `--runtime-config=batch/v2alpha1=tr 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). -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 Here is an example Cron Job. Every minute, it runs a simple job to print current time and then say