Merge pull request #54920 from tengqm/improve-cronjob-doc

Automatic merge from submit-queue. If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>.

Improve cronjob concurrency policy doc

**What this PR does / why we need it**:
The CronJob API documentation (https://kubernetes.io/docs/api-reference/v1.8/#cronjobspec-v1beta1-batch) did not clearly state what can be used as `concurrencyPolicy`. Instead, it only says that the default value is "Raw".

**Which issue(s) this PR fixes**:

**Special notes for your reviewer**:
This patch is not changing any code logic but it involves generated "code".

**Release note**:
```release-note
NONE
```
This commit is contained in:
Kubernetes Submit Queue
2017-11-07 21:34:11 -08:00
committed by GitHub
12 changed files with 28 additions and 13 deletions

View File

@@ -70759,7 +70759,7 @@
],
"properties": {
"concurrencyPolicy": {
"description": "Specifies how to treat concurrent executions of a Job. Defaults to Allow.",
"description": "Specifies how to treat concurrent executions of a Job. Valid values are: - \"Allow\" (default): allows CronJobs to run concurrently; - \"Forbid\": forbids concurrent runs, skipping next run if previous run hasn't finished yet; - \"Replace\": cancels currently running job and replaces it with a new one",
"type": "string"
},
"failedJobsHistoryLimit": {
@@ -70894,7 +70894,7 @@
],
"properties": {
"concurrencyPolicy": {
"description": "Specifies how to treat concurrent executions of a Job. Defaults to Allow.",
"description": "Specifies how to treat concurrent executions of a Job. Valid values are: - \"Allow\" (default): allows CronJobs to run concurrently; - \"Forbid\": forbids concurrent runs, skipping next run if previous run hasn't finished yet; - \"Replace\": cancels currently running job and replaces it with a new one",
"type": "string"
},
"failedJobsHistoryLimit": {