John Schnake

When figuring out which versions are supported for `sonobuoy e2e` you have to come to github and know where to look. It would be better to be able to dump...

Develop way to simulate airgap locally and in CI

1

The airgap example is always painful to try and reproduce and we don't have a great story for users even though we've done so much to make things easier. We...

The page https://sonobuoy.io/docs/v0.56.8/e2eplugin/ talks about the plugins, dry run mode, but doesnt even mention the `sonobuoy e2e` command which is particularly relevant since it helps you choose the focus/skip values...

We've done 2 different TGIK episodes about Sonobuoy and another youtube video or two. We should surface those better in our docs.

We implemented basic plugin management but haven't had time to make much use of it. We could further move logic out of the codebase if we do a few things...

Now that @andrewyunt implemented the basic ordering of plugins we could remove all the query logic entirely into its own plugin. This would simplify the codebase and make it easier...

We have all sorts of query options and they are never documented at all making them difficult to use at all.

The e2e command uses data that we gather from k8s releases; we need to automate that. Currently its a multistep process and manual (but documented)

Need to update the cron job issues to use the new labels we used instead of the legacy/release one

What other plugin result formats should Sonobuoy be able to process?

6

Currently Sonobuoy plugins specify that they either produce `raw` or `junit` output. If producing `junit`, Sonobuoy knows to look for an XML file and to parse it as JUnit. This...