Rename Scheduled Job to Cron Job

Author: soltysh

_topic_map.yml

@@ -681,8 +681,8 @@ Topics:
     File: environment_variables
   - Name: Jobs
     File: jobs
-  - Name: Scheduled Jobs
-    File: scheduled_jobs
+  - Name: Cron Jobs
+    File: cron_jobs
   - Name: Revision History
     File: revhistory_dev_guide
     Distros: openshift-enterprise,openshift-dedicated

dev_guide/scheduled_jobs.adoc renamed to dev_guide/cron_jobs.adoc

@@ -1,5 +1,5 @@
-[[dev-guide-scheduled-jobs]]
-= Scheduled Jobs
+[[dev-guide-cron-jobs]]
+= Cron Jobs
 {product-author}
 {product-version}
 :data-uri:
@@ -13,53 +13,53 @@ toc::[]
 
 == Overview
 
-A _scheduled job_ builds on a regular
+A _cron job_ builds on a regular
 xref:../dev_guide/jobs.adoc#dev-guide-jobs[job] by allowing you to specifically
-schedule how the job should be run. Scheduled jobs are part of the
-link:http://kubernetes.io/docs/user-guide/scheduled-jobs[Kubernetes] API, which
+schedule how the job should be run. Cron jobs are part of the
+link:http://kubernetes.io/docs/user-guide/cron-jobs[Kubernetes] API, which
 can be managed with `oc` commands like other
 xref:../cli_reference/basic_cli_operations.adoc#object-types[object types].
 
 ifdef::openshift-enterprise[]
 [NOTE]
 ====
-As of {product-title} 3.3.1, Scheduled Jobs is a feature in Technology Preview.
+As of {product-title} 3.3.1, Cron Jobs is a feature in Technology Preview.
 ====
 endif::[]
 
-[[creating-a-scheduledjob]]
-== Creating a Scheduled Job
+[[creating-a-cronjob]]
+== Creating a Cron Job
 
-A scheduled job configuration consists of the following key parts:
+A cron job configuration consists of the following key parts:
 
 * A schedule specified in link:https://en.wikipedia.org/wiki/Cron[cron format].
 * A job template used when creating the next job.
 * An optional deadline (in seconds) for starting the job if it misses its
 scheduled time for any reason. Missed jobs executions will be counted as failed
 ones. If not specified, there is no deadline.
 * `*ConcurrencyPolicy*`: An optional concurrency policy, specifying how to treat
-concurrent jobs within a scheduled job. Only one of the following concurrent
+concurrent jobs within a cron job. Only one of the following concurrent
 policies may be specified. If not specified, this defaults to allowing
 concurrent executions.
-** `Allow` allows Scheduled Jobs to run concurrently.
+** `Allow` allows Cron Jobs to run concurrently.
 ** `Forbid` forbids concurrent runs, skipping the next run if the previous has not
 finished yet.
 ** `Replace` cancels the currently running job and replaces
 it with a new one.
-* An optional flag allowing the suspension of a scheduled job. If set to `true`,
+* An optional flag allowing the suspension of a cron job. If set to `true`,
 all subsequent executions will be suspended.
 
-The following is an example of a `*ScheduledJob*` resource:
+The following is an example of a `*CronJob*` resource:
 
 ====
 [source,yaml]
 ----
 apiVersion: batch/v2alpha1
-kind: ScheduledJob
+kind: CronJob
 metadata:
   name: pi
 spec:
-  schedule: */1 * * * ?    <1>
+  schedule: "*/1 * * * *"  <1>
   jobTemplate:             <2>
     spec:
       template:
@@ -74,25 +74,3 @@ spec:
 1. Schedule for the job. In this example, a job will run every minute.
 2. Job template. This is similar to the xref:../dev_guide/jobs.adoc#creating-a-job[job example].
 ====
-
-ifdef::openshift-enterprise[]
-[[scheduledjob-known-issues]]
-== Known Issues
-
-[[scheduledjob-known-issues-unable-to-edit]]
-=== Unable to Edit a Scheduled Job
-
-There is a link:https://bugzilla.redhat.com/show_bug.cgi?id=1378368[known issue]
-when invoking `oc edit scheduledjob` due to an error that was already fixed in
-the latest version. However, due to significant code changes, this was not
-backported.
-
-One possible solution is to use `oc patch` command instead of `oc edit`.
-
-[[scheduledjob-known-issues-change-concurrency]]
-=== Unable to Change Concurrency Policy
-
-There is a link:https://bugzilla.redhat.com/show_bug.cgi?id=1386463[known issue]
-when changing concurrency policy where no new jobs are created after that
-operation is run. The issue is still under investigation in the latest version.
-endif::[]