From 7feeffcc3e54e7c9d0b0078ff02a97f68ad16961 Mon Sep 17 00:00:00 2001 From: Qiming Teng Date: Tue, 2 Jan 2018 17:53:08 +0800 Subject: [PATCH] Improve CronJobs doc This PR adds text about restarting apiserver and controller-manager component. Closes: #3710 --- docs/concepts/workloads/controllers/cron-jobs.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/concepts/workloads/controllers/cron-jobs.md b/docs/concepts/workloads/controllers/cron-jobs.md index e424aa4e5f..9d5a292841 100644 --- a/docs/concepts/workloads/controllers/cron-jobs.md +++ b/docs/concepts/workloads/controllers/cron-jobs.md @@ -37,7 +37,8 @@ A typical use case is: You need a working Kubernetes cluster at version >= 1.8 (for CronJob). For previous versions of cluster (< 1.8) you need to explicitly enable `batch/v2alpha1` API by passing `--runtime-config=batch/v2alpha1=true` to 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). +for more), and then restart both the API server and the controller manager +component. ## Creating a Cron Job