53ee76fe1a
When job.spec.completions is nil, only one task needs to succeed for the job to succeed, and parallelism can be scaled freely during runtime. Added tests. Release Note: This causes two minor changes to the API. First, unset parallelism previously was defaulted to be equal to completions. Now it always defaults to 1 if unset. Second, having parallelism=N and completions unset would previously be defaulted to 1 completion and N parallelism. (this is not something we expect people to do, though) Now, no defaulting occurs in that case, and the job's behavior is different (any completion causes success).
20 lines
339 B
YAML
20 lines
339 B
YAML
apiVersion: extensions/v1beta1
|
|
kind: Job
|
|
metadata:
|
|
name: job-wq-2
|
|
spec:
|
|
selector:
|
|
matchLabels:
|
|
app: job-wq-2
|
|
parallelism: 2
|
|
template:
|
|
metadata:
|
|
name: job-wq-2
|
|
labels:
|
|
app: job-wq-2
|
|
spec:
|
|
containers:
|
|
- name: c
|
|
image: gcr.io/myproject/job-wq-2
|
|
restartPolicy: OnFailure
|