How can you scale out a Job that is already created?

Related searches

I have a Kubernetes Job that has, for instance, parallelism set to 4. When this job is created, I might want to scale this out to, say, 8. But it seems like editing the Job and setting parallelism to 8 doesn't actually create more pods in the Job.

Am I missing something? Or is there no way to scale out a Job?

Thanks in advance!

So as per job documentation you can still scale a Job running the following command:

kubectl scale job my-job --replicas=[VALUE]

Simple test shows that this option works right now as expected, but will be really deprecated in a future

kubectl scale job is DEPRECATED and will be removed in a future version.

The ability to use kubectl scale jobs is deprecated. All other scale operations remain in place, but the ability to scale jobs will be removed in a future release.

The reason is: Deprecate kubectl scale job

Use below Job yaml as an example to create job:

apiVersion: batch/v1
kind: Job
  name: test-job
      - name: pi
        image: perl
        command: ["perl",  "-Mbignum=bpi", "-wle", "print bpi(2010)"]
      restartPolicy: Never
  completions: 1000
  parallelism: 5

Now lets test behavior:

kubectl describe jobs.batch test-job 
Parallelism:    5
Completions:    1000
Start Time:     Fri, 17 May 2019 16:58:36 +0200
Pods Statuses:  5 Running / 21 Succeeded / 0 Failed

kubectl get pods | grep test-job | grep Running
test-job-98mlv           1/1     Running     0          13s
test-job-fs2hb           1/1     Running     0          8s
test-job-l8n6v           1/1     Running     0          16s
test-job-lbh46           1/1     Running     0          13s
test-job-m8btl           1/1     Running     0          2s

Changing parallelism with kubectl scale:

kubectl scale jobs.batch test-job --replicas=10

kubectl describe jobs.batch test-job
Parallelism:    10
Completions:    1000
Start Time:     Fri, 17 May 2019 16:58:36 +0200
Pods Statuses:  10 Running / 87 Succeeded / 0 Fail

kubectl get pods | grep test-job | grep Running
test-job-475zf           1/1     Running     0          10s
test-job-5k45h           1/1     Running     0          14s
test-job-8p99v           1/1     Running     0          22s
test-job-jtssp           1/1     Running     0          4s
test-job-ltx8f           1/1     Running     0          12s
test-job-mwnqb           1/1     Running     0          16s
test-job-n7t8b           1/1     Running     0          20s
test-job-p4bfs           1/1     Running     0          18s
test-job-vj8qw           1/1     Running     0          18s
test-job-wtjdl           1/1     Running     0          10s

And the last step that i believe will be the most interesting for you - you can always edit your job using kubectl patch command

kubectl patch job test-job -p '{"spec":{"parallelism":15}}'

kubectl describe jobs.batch test-job
Parallelism:    15
Completions:    1000
Start Time:     Fri, 17 May 2019 16:58:36 +0200
Pods Statuses:  15 Running / 175 Succeeded / 0 Failed

kubectl get pods | grep test-job | grep Running | wc -l

Creating a Scale Out Backup Repository in Veeam, If a job is already backing up to a repository that you select, it will automatically target the SOBR for future jobs. Some repositories cannot be� In order to scale your operations, you must have repeatable processes for every role in your business. With Tallyfy, you can easily define and measure every step of your workflow. The tracker will allow you to identify problems, progress, and delays. And because we know that not all processes follow the same path, it is easily adaptable.

There's a scale command:

kubectl scale job my-job --replicas=[VALUE]

From docs:

kubectl scale causes the number of concurrently-running Pods to change. Specifically, it changes the value of parallelism to the [VALUE] you specify.

Cant Add Repository to a Scale Out Backup Repository?, When adding repositories to a Veeam Scale Out Backup Repository;Unable to add If you didn't already know, the Backup-Configuration-Job, is a backup of the It gets created automatically, and gets put into your first created repository. Be clear about the potential up-sides to job rotation or job-swapping. If you're simply rotating a new employee from department to department, the program provides more hands on deck.

Moving Existing Jobs to New Scale-out Repository, What is the best way to move existing backup files to a new Scale-out on each job (unless this was already configured on the original repo). I just created a Scale-out repo that encompasses all of the EqualLogic volumes. “You have to know that it is happening, and you have to plan for it.” Research your options. Let people know when and why they will max out and then what options are available moving forward.

Scale-Out Backup Repository, A scale-out backup repository is a repository system with horizontal scaling A scale-out backup repository can be used for the following types of jobs and tasks � If you are concerned about your job responsibilities being changed, it's a good idea to see if you can discuss the situation with your manager or your company's Human Resources department to see if there is a way you can work out a solution that is agreeable to everyone involved.

Step By Step: Creating a Scale-out Backup Repository in Veeam 9 , Step By Step: Creating a Scale-out Backup Repository in Veeam 9 Previously it would have been a real pain to leverage all of these as you for each 'island' and then maintain the jobs to make sure that a) there will be� And with the kubectl command you could scale them from 11 to 3 like so: kubectl scale deployments/nginx-deployment --replicas=3. You could even scale them down to 0 if you need.

Scale out is a growth architecture or method that focuses on horizontal growth, or the addition of new resources instead of increasing the capacity of current resources (known as scaling up). In a system such as a cloud storage facility, following a scale-out growth would mean that new storage hardware and controllers would be added in order to

  • That's deprecated and will be removed. Also, changing the value of parallelism to a higher value doesn't actually add additional pods.
  • Maybe kubectl scale --replicas=[VALUE] job/my-job. Or you're saying that scale is deprecating in general? I'm on the latest kubectl and don't see the deprecation notice.
  • Say I have 10 jobs running and I reduce parallelism to 5, is there a way to know which of the 10 jobs will be terminated? Or can this be manually specified somehow?