File tree Expand file tree Collapse file tree 1 file changed +7
-3
lines changed
content/en/docs/concepts/workloads/controllers Expand file tree Collapse file tree 1 file changed +7
-3
lines changed Original file line number Diff line number Diff line change @@ -38,6 +38,7 @@ You can run the example with this command:
38
38
``` shell
39
39
kubectl apply -f https://kubernetes.io/examples/controllers/job.yaml
40
40
```
41
+ The output is similar to this:
41
42
```
42
43
job.batch/pi created
43
44
```
@@ -47,6 +48,7 @@ Check on the status of the Job with `kubectl`:
47
48
``` shell
48
49
kubectl describe jobs/pi
49
50
```
51
+ The output is similar to this:
50
52
```
51
53
Name: pi
52
54
Namespace: default
@@ -91,6 +93,7 @@ To list all the Pods that belong to a Job in a machine readable form, you can us
91
93
pods=$( kubectl get pods --selector=job-name=pi --output=jsonpath=' {.items[*].metadata.name}' )
92
94
echo $pods
93
95
```
96
+ The output is similar to this:
94
97
```
95
98
pi-5rwd7
96
99
```
@@ -398,10 +401,11 @@ Therefore, you delete Job `old` but _leave its pods
398
401
running_, using `kubectl delete jobs/old --cascade=false`.
399
402
Before deleting it, you make a note of what selector it uses :
400
403
401
- ` ` `
404
+ ` ` ` shell
402
405
kubectl get job old -o yaml
403
406
` ` `
404
- ```
407
+ The output is similar to this :
408
+ ` ` ` yaml
405
409
kind: Job
406
410
metadata:
407
411
name: old
@@ -420,7 +424,7 @@ they are controlled by Job `new` as well.
420
424
You need to specify `manualSelector : true` in the new Job since you are not using
421
425
the selector that the system normally generates for you automatically.
422
426
423
- ```
427
+ ` ` ` yaml
424
428
kind: Job
425
429
metadata:
426
430
name: new
You can’t perform that action at this time.
0 commit comments