Closed eatoncns closed 3 years ago
Does the create job function make sure the pod is available and the command was executed on it first - Is it possible to do that?
What we look at for job completion is the status for pulled job. The only relevant thing I could see there was active number of running pods but when I tested it seemed to go to 1 before pod is available
Although looking at the CLI output there is a job status of "running"... will see what that corresponds to
I checked the job status conditions and there is a single transition from None
to type Complete
when it succeeds :(
Purpose of PR
Currently the create job function waits for job to complete. As part of moving crawlers to jobs in kubernetes cluster we want to be able to kick off long running job and not wait for completion.
I looked at waiting for active field in job being > 1 but this seems to be more related to pod existing than being available and running so not sure it adds much value
Closes #87