From 95b51e46e4e1af4358e7fad8b93c85f4372c54dc Mon Sep 17 00:00:00 2001 From: Maciej Szulik Date: Wed, 9 Mar 2016 10:21:04 +0100 Subject: [PATCH] Removed v1beta1 disclaimer for jobs, since jobs are now part of batch/v1 --- docs/user-guide/jobs.md | 14 +++----------- 1 file changed, 3 insertions(+), 11 deletions(-) diff --git a/docs/user-guide/jobs.md b/docs/user-guide/jobs.md index e2fd8a8a2c..7baafcac3f 100644 --- a/docs/user-guide/jobs.md +++ b/docs/user-guide/jobs.md @@ -88,9 +88,9 @@ the same schema as a [pod](/docs/user-guide/pods), except it is nested and does `kind`. In addition to required fields for a Pod, a pod template in a job must specify appropriate -labels (see [pod selector](#pod-selector) and an appropriate restart policy. +labels (see [pod selector](#pod-selector)) and an appropriate restart policy. -Only a [`RestartPolicy`](/docs/user-guide/pod-states) equal to `Never` or `OnFailure` are allowed. +Only a [`RestartPolicy`](/docs/user-guide/pod-states/#restartpolicy) equal to `Never` or `OnFailure` are allowed. ### Pod Selector @@ -331,15 +331,7 @@ driver, and then cleans up. An advantage of this approach is that the overall process gets the completion guarantee of a Job object, but complete control over what pods are created and how work is assigned to them. -## Caveats - -Job objects are in the [`extensions` API Group](/docs/api/#api-groups). - -Job objects have [API version `v1beta1`](/docs/api/)#api-versioning). Beta objects may -undergo changes to their schema and/or semantics in future software releases, but -similar functionality will be supported. - ## Future work Support for creating Jobs at specified times/dates (i.e. cron) is expected in the next minor -release. \ No newline at end of file +release.