Logs utility could show more info at the start

[Turbots]

When running kpack in a specific namespace (not the default namespace) and you run the logs utlity, there is literally no output, the logs utility just hangs and shows nothing.

First time troubleshooting can be very confusing, since the build pod is running and maybe failing, but you cannot see why through the logs utility.

Only by adding the -namespace flag, it starts working and actual logs (and possible errors) show up.

So it this may seem like "duh, you need to add the namespace to the command", this didn't seem so obvious from a first user's perspective.

What would help is an output line at the start indicating something like: Showing output for image <image-name> in namespace <namespace>

That way, I would have immediately noticed it was polling logs in the wrong namespace.

[benmoss]

I ran into this issue too. It's pretty unintuitive that it hangs with no arguments, and also with any valid arguments that cause it to look up a build that doesn't exist on the targeted API server.