Optional job log streaming

[wyrie]

Hey. We just started using the tool and one thing we would like to have is the ability to not stream the logs from the job during kube-job execution.

Why? We execute kube-job from within a pod in the cluster and want to offload some long running ad-hoc commands to it. We can't always keep the connection to the pod open, so we would like to run kube-job without the --container argument so that it will create the job but then drop back to shell.

We can then inspect the pod logs at some future date for results.

Does that sound feasible to you?

[h3poteto]

Making container argument optional is not a bad idea. But I don't understand why that would solve your issue. Is it just a hassle to not want to specify the container, or is there some obvious reason why you don't know the container name?

[wyrie]

Knowning the container name or typing the argument is fine. I just thought the argument's purpose is to watch the log, from help message:

--container string       Container name which you want watch the log

So if you don't provide one it could mean you don't want to watch the log? Or maybe it's better to be more explicit and add a --no-watch arg.

[wyrie]

Made some proposals in this PR. The container argument seems to have a dual purpose currently.

[h3poteto]

Ah, I got it a little bit now. You want to execute a job, but you don't need to watch the logs, so you feel that container argument is unnecessary for you usecase.