What's the point of

args

and

command

being different parameters? Couldn't it all be a command with args passed as well?

Assuming the generic context of K8s/containers: Command can be default, args can be custom. if my image is built with

tail

as the command I can pass

<filename>

or

-f

etc as args, however I don't want to override

tail

with

cat

. It is actually quite significant in distroless images where passing a custom command would not succeed if the image was built with only a single binary and its runtime deps.

ah I see, ty for making it clear

I can completely feel you, I had challenges with kernels and loading drivers for PCI cards or Hypervisor internals

With this information I gather that the kubernetes-exec aciton types should only have the

spec.command

field as the original container entry point is relevant and we're running a command in the container. @swift-garage-61180 does that make sense?

Yeah, sounds good.