From b4068fb73cb6976c0893d3a68b16e481eeb9ae7e Mon Sep 17 00:00:00 2001 From: Maciej Szulik Date: Thu, 8 Mar 2018 21:36:58 +0100 Subject: [PATCH] Remove job's scale-related operations (#7684) --- .../workloads/controllers/jobs-run-to-completion.md | 10 ---------- 1 file changed, 10 deletions(-) diff --git a/docs/concepts/workloads/controllers/jobs-run-to-completion.md b/docs/concepts/workloads/controllers/jobs-run-to-completion.md index d9add2d526368..b582e0e6fb98b 100644 --- a/docs/concepts/workloads/controllers/jobs-run-to-completion.md +++ b/docs/concepts/workloads/controllers/jobs-run-to-completion.md @@ -151,16 +151,6 @@ The requested parallelism (`.spec.parallelism`) can be set to any non-negative v If it is unspecified, it defaults to 1. If it is specified as 0, then the Job is effectively paused until it is increased. -A job can be scaled up using the `kubectl scale` command. For example, the following -command sets `.spec.parallelism` of a job called `myjob` to 10: - -```shell -$ kubectl scale --replicas=10 jobs/myjob -job "myjob" scaled -``` - -You can also use the `scale` subresource of the Job resource. - Actual parallelism (number of pods running at any instant) may be more or less than requested parallelism, for a variety of reasons: