Sonobuoy v0.16.2
What's new
Piping data into sonobuoy run
In cases where large changes to YAML from sonobuoy gen need to occur, we've recommended piping the data then to kubectl apply -f - to start the run. However, when you do that you lose out on the ability to use the --wait flag which can be very helpful.
We decided to add a -f flag to sonobuoy run so that you can load files or pipe to it from stdin. For example:
$ sonobuoy gen > my.yaml
$ cat my.yaml | sonobuoy run -f -
This may be a very useful feature for users who routinely need to change parts of the YAML since you can include other tools as well:
sonobuoy gen | <commands to change the yaml> | sonobuoy run -f -
What's better
Improved documentation
Documentation doesn't always get the attention it deserves. As we've been more active with Sonobuoy development in the past few months a number of shortcomings have been noted and we tried to clarify things and improve organization.
Clear timeouts
One relatively common failure mode is that the plugins fail to provide results within the timeout period. Historically when this happens users would get partial results from the e2e plugin which could be misleading since it may appear that N tests passed but it wasn't clear that some were not run at all. In addition, the logs noted the timeout, but the ended up in the middle of all the logs and it was difficult to notice.
As a result, we added more logging and tried to put it in more visible places. In addition, we made changes to the results processing logic that would be aware of problems like this and mark the plugins as having a status of timeout. Hopefully these changes will save hours of unnecessary debugging.
Bug fixes
- Fixed a bug which caused some nodes results from a daemonset plugin to not be considered when doing post-processing.
- Fixed a bug where a plugin which failed to run wouldn't have its
errorsdirectory considered during post-processing leading to an "unknown" status instead of a failure.
Other
- Blog post on how to customize the E2E test image and run with unique testing options set: blog
- Moved from Travis to CircleCI
- Moved from gcr.io to DockerHub for image hosting
- Updated imports for the new Github org
Changelog
9b83cac Don't set branch just let it be calculated (#966)
a16e3e4 Tweaks to CI (#964)
3d0a548 Fixing up CI scripts to publish correctly (#963)
fe2646f Adjust our CircleCI to list tags on required job (#961)
7295394 Add older blog posts and author images (#958)
0838111 Prepare v0.16.2 release (#957)
26cb536 Update release process docs to reference new systems (#956)
6077455 Improve docs organization and E2E descriptions (#951)
3d03f98 Make timeouts more clear (#938)
bb1398c Remove .travis.yml to disable TravisCI (#954)
71dd2f9 Update badge to be from CircleCI not Travis (#953)
a673ac1 Unity integration testing and remove Travis (#949)
381d9e9 Make the publish script executable (#948)
be325ce Fixup to path to script (#947)
ff5326e Move image pushing into CircleCI (#945)
03e44e6 Adds new blog post regarding customizing the E2E test image (#944)
6899c87 Add CircleCI config (#940)
e18111d Update README to download release instead of go get (#942)
1e57ed8 Move to go modules (#935)
2686723 Results aggregation should consider the errors directory (#936)
69cc7ff Process all nodes and treat empty status as unknown (#937)
61cb07b Fixup to docker image push (#934)
03fd8b6 Get dockerhub image pushing to work on Travis (#932)
7218d76 Use created namespace name during run --wait (#930)
15ab7f3 Update our registry to dockerhub and use our latest kind-node (#927)
c799770 Fix blockquote rendering (#923)
4ba8b74 Add new GitHub org blog post (#928)
3290552 Allow piping input to sonobuoy run (#925)
3a8f83a Update repo throughout codebase (#924)