Skip to content

v0.15.4
Compare
Choose a tag to compare
@heptibot heptibot released this 17 Sep 20:16
v0.15.4
3d6c1be
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Sonobuoy v0.15.4

What's new

  • Supported modes

The supported "modes" for sonobuoy run have changed. The supported values are now quick, non-disruptive-conformance, and certified-conformance. This is due to Kubernetes changes in v1.16 which will be allowing disruptive tests to be included in Conformance runs. Sonobuoy, by default, will seek to protect your workloads by avoiding those disruptive tests unless you explicitly state that you want to run in certified-conformance mode.

To be clear, sonobuoy run is most appropriate as a safe way to test that your cluster is in a good state.
sonobuoy run --mode certified-conformance will run all the conformance tests for submission to the CNCF Certified Kubernetes program.

  • Progress updates

Sonobuoy now has support for collecting and reporting on the progress of plugins while they are still running. This functionality is currently just in Sonobuoy itself and is not yet implemented in the upstream E2E tests, where it is most useful. A new [example][https://github.com/heptio/sonobuoy/tree/master/examples/plugins/progress-reporter] has been added to illustrate how you can utilize this functionality in your own plugins.

What's better

  • In v1.16 Kubernetes has a few E2E tests which may evict user workloads from a node (see the above item about certified-conformance mode. To ensure that Sonobuoy and your plugins run appropriately and do not get evicted, a new toleration is added by default.
  • When tailing logs via sonobuoy logs -f, if Sonobuoy sees a container but it is not yet running, we will continue to watch the container and start streaming logs once it enters the running state.
  • If a plugin fails to report any results and is considered an unknown result, that will bubble up and cause the plugin to properly be marked as unknown rather than passed by default. This reduces the number of false positives possible.

Changelog

3d6c1be Bump version and add v0.15.4 docs (#886)
90a586f Add certified conformance mode and non-disruptive-conformance mode (#885)
cb43587 Progress reports for plugins (#869)
8bd715b Remove 'extended' mode (#884)
9eae93e Minor change to retrigger blog publishing (#882)
06fcf66 Add blog post for Customizing PodSpecs (#879)
f7e2366 Add a disruptive taint to list of default tolerations (#878)
0f9e963 check for container running before following logs (#706)
e03eebd Remove unnecessary legacy branding (#873)
cfde6a0 Update to Go 1.13 (#871)
3975a9e Show logs for a specific plugin (#868)
bc64713 Adjust MASTER_URL to be just the hostname (#867)
a603fdb Bubble up unknown results just like failures (#866)
bfa3ade Fix broken links and reference to conformance image (#864)

Assets 6
Loading