Run kubectl cluster-info dump after each test session.
Currently not the best debugging tool but should definitely help
- results of all test cases are grouped together
- hard to browse, maybe better if results were just zipped so they could be browsed locally? On the other hand it's nice to open logs in the browser
- system logs and config are going to be noise for the most part
- results of kubectl describe would be useful for the class of errors involving configuration
Buildkite does no garbage collection of these, that will be up to us to figure out at some point