improve logging

[BenTheElder]

• make log level configurable
• improve differentiation between print, info, debug etc.
  • we should use print & friends for normal user level info
  • use info for debug-ish details like "running this command"
  • use debug for trace-ish level details
  • use warn & error as appropriate
• revisit structured logging
• look at adding "quiet" modes to all commands

/kind cleanup
/assign

[BenTheElder]

I've done most of this
/lifecycle active

[BenTheElder]

xref: #109

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[BenTheElder]

still a major issue, probably will switch to klog / logr to match the ecosystem and rework what we log then...

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[BenTheElder]

/remove-lifecycle stale

[BenTheElder]

this is more or less done now, we can make the logger a little nicer but we've improved a lot here