Make it possible to specify the .Command field of the Kubernetes Container struct

[advdv]

Currently it is not possible to specify the command of a container when using nerd job run. For what use cases do we need this and how can we separate .Command from .Args?

[advdv]

@Overv Could you provide a usecase/container that requires this to be available to the CLI?

[Overv]

I can't really think of any use cases that absolutely require it right now. It seems that most people only use it to inspect containers by executing bash, which is not a relevant use case for our platform. Even rancher, which uses a single image for starting kubelet, controller-manager, etc. passes the binary to start as an argument instead of a command.

Users will have the following alternatives:

• Build their own image
• Run a generic image like busybox or Ubuntu, where they can pass arbitrary commands to the shell