Merge pull request #35516 from spurin/job_suspension_context

Added supporting context for job suspension functionality

Author: k8s-ci-robot

content/en/docs/concepts/workloads/controllers/job.md

@@ -510,8 +510,7 @@ When a Job is resumed from suspension, its `.status.startTime` field will be
 reset to the current time. This means that the `.spec.activeDeadlineSeconds`
 timer will be stopped and reset when a Job is suspended and resumed.
 
-Remember that suspending a Job will delete all active Pods. When the Job is
-suspended, your [Pods will be terminated](/docs/concepts/workloads/pods/pod-lifecycle/#pod-termination)
+When you suspend a Job, any running Pods that don't have a status of `Completed` will be [terminated](/docs/concepts/workloads/pods/pod-lifecycle/#pod-termination).
 with a SIGTERM signal. The Pod's graceful termination period will be honored and
 your Pod must handle this signal in this period. This may involve saving
 progress for later or undoing changes. Pods terminated this way will not count
@@ -537,6 +536,20 @@ spec:
       ...
 ```
 
+You can also toggle Job suspension by patching the Job using the command line.
+
+Suspend an active Job:
+
+```shell
+kubectl patch job/myjob --type=strategic --patch '{"spec":{"suspend":true}}'
+```
+
+Resume a suspended Job:
+
+```shell
+kubectl patch job/myjob --type=strategic --patch '{"spec":{"suspend":false}}'
+```
+
 The Job's status can be used to determine if a Job is suspended or has been
 suspended in the past: