v0.20.0

Sonobuoy v0.20.0

What's new

We decoupled Sonobuoy releases from Kubernetes versions and announced our roadmap towards v1.0, let us know what you think!

Changelog

f6e1914 Release 0.20 (#1198)
f5437c1 Use "stale" label for stale bot (#1200)
75fb977 Merge pull request #1201 from vladimirvivien/toward1-blog
9617f99 Blog annoucing vision and roadmap
fa53698 Add Docker Hub rate limit workaround (#1194)
0c072ef Dynamically determine image of plugins (#1192)
df8d4eb Create codeql-analysis.yaml (#1193)
0f7c90c Merge pull request #1190 from wilsonehusin/remove-contributors
f911864 Use Kramdown instead of Redcarpet
031d604 Update Jekyll and therefore Kramdown
35dc86e Update Jekyll
dff8ef4 Remove contributors section
185c859 go 1.15 + unit test + lint/sync workflows (#1186)
3e0f8ed Add StaleBot (#1184)
be8c386 Deterministic TagPair assertion of custom registry (#1183)
7419e1d Add golangci-lint on GitHub Actions with fixes (#1179)
883fc90 Merge pull request #1169 from vladimirvivien/inventory-plugin-doc
e5b16ea Adding cluster inventory plugin doc

Release v0.19.0

This release is to add support for the newly release Kubernetes version of 1.19.0.

What's new

This release does not introduce any new change in functionality.

Starting with this release, however, the policy for supported E2E images for air-gap support will be applied as described in the document. Meaning, the current binary will adhere to the two-version regression from the current release where Sonobuoy will only run and download E2E test images for Kubernetes version 1.18 and 1.17 only. To test for an earlier version of Kuberentes, please use an earlier release of Sonobuoy.

Changelog

e03f9ee Merge pull request #1160 from vladimirvivien/sonobuoy-release-0.19.0
ec4cefd Release for Kubernetes 1.19.0
670b310 Merge pull request #1159 from vladimirvivien/sonobuoy-release-0.18.5
ecddf13 Prepare for v0.18.5 release

v0.18.5

Release v0.18.5

This is a release with minimal changes. It mainly does the followings:

• Fixes a CVE that was found in a Ruby gem used to generate the site for Sonobuoy
• Update the Kubernetes client-go package to version 0.18.5
• Update the description of ---wait parameter to inculde minutes as the unit.

Changelog

a79a43a Merge pull request #1123 from zubron/fix-formatting-of-config-docs
83d59f2 Fix formatting on docs pages
0b9a839 Upgrade Kubernetes client libraries to 0.18.5 (#1138)
086e048 Update args.go (#1127)
47e90ec Merge pull request #1155 from vmware-tanzu/dependabot/bundler/site/kramdown-2.3.0
b7d9de6 Bump kramdown from 1.17.0 to 2.3.0 in /site
ec68203 Merge pull request #1154 from vladimirvivien/update-kramdown-gem-version
1d8d0b2 Update gem kramdown for site generation

v0.18.4

Sonobuoy v0.18.4

Conformance image registry changes

Sonobuoy v0.18.4 now uses k8s.gcr.io as the registry to pull the conformance image from as gcr.io/google-containers is no longer being used and is now read-only. Older versions of Sonobuoy which are being used to test older versions of Kubernetes will continue to work as the conformance images for those older Kubernetes versions will still be accessible from gcr.io/google-containers. See #1146 for more details.

For testing clusters where the version is greater than v1.18.6 or for new patch releases of older versions, users will need to update to the latest version of Sonobuoy to ensure that the correct registry is used or override the conformance image used by Sonobuoy by using the flag --kube-conformance-image.

Removal of non-inclusive language

• The MasterURL field of WorkerConfig has been renamed to AggregatorURL. The environment variable for setting that field when starting a worker container has been changed from MASTER_URL to AGGREGATOR_URL. This will break compatibility between versions of Sonobuoy, however it will only affect users who manually edit the manifest produced by Sonobuoy to run different image versions for the aggregator and worker. Sonobuoy image version v0.18.3 and earlier can be used as the aggregator with workers that use image versions v0.18.4 and later. Sonobuoy image version v0.18.4 and later cannot be used as the aggregator image with workers that use image version v0.18.3 and earlier. We strongly recommend that you use the same version of the image for both the aggregator and the workers. From v0.19.0 onwards, and backwards compatibility between image versions will be dropped and using different image versions for the aggregator and worker will not be supported. (#1141)

• The label for identifying the aggregator pod is now sonobuoy-component: aggregator (replacing run: sonobuoy-master). The label run: sonobuoy-master is still applied but is now deprecated and its use will be removed in a later release. Once removed, older clients will not be able to query runs started by newer versions of Sonobuoy which do not use this label. A warning about the deprecated label will now be printed if using a newer client to query a run created by an older version. (#1139)

• Removed the "master" alias from the aggregator command. (#1137)

Changelog

b5e4803 Prepare v0.18.4 release (#1148)
e957f84 Remove use of gcr.io/google-containers (#1146)
019d1e0 Use latest Sonobuoy webinar as the overview video (#1144)
68b845a Replace use of master in Windows Dockerfile (#1143)
392d68e Replace MasterURL with AggregatorURL in WorkerConfig (#1141)
5f1730b Remove unused config file handling from worker (#1142)
046c082 Remove insensitive language from old docs (#1140)
750f015 Remove use of "master" in labels and names (#1139)
e43cefe Remove alias for aggregator command (#1137)
81fa9a7 Bump to k8s.io/* to v0.17.7 and tidy deps (#1135)
fa6e29f Replace use of whitelist with allow/allow list (#1132)

v0.18.3

Sonobuoy v0.18.3

What's better

• The Sonobuoy Results format now uses map[string]interface{} as the type for the details field. This allows arbitrary data to be included in this field. For compatibility with other results processing operations, only string keys should be used in any maps contained within this field.
• The delete --all command will now identify namespaces for deletion by checking for the presence of the e2e-framework and e2e-run labels instead of the e2e- name prefix.
• The default value for e2e plugin environment variable E2E_PARALLEL has been changed to "false" as the upstream script that consumes the value expects it to be boolean.

Changelog

3e8a10e Prepare v0.18.3 release (#1131)
03ae14e Allow arbitrary data in Details map in results (#1130)
c4956c0 Improve E2E namespace cleanup (#1126)
385f41e Change default value for E2E_PARALLEL (#1124)
e1a28d2 README.md: Fix broken link to docker (#1121)
f862e4b Add blog post for who-can plugin (#1120)

v0.18.2

Sonobuoy v0.18.2

What's better

• The results command now includes result items with custom statuses in the total results count. It also includes these custom statuses and their count in the result report.

Changelog

f13b4cc Prepare v0.18.2 release (#1117)
bbd55f7 Include custom status in results report (#1116)
1a31818 Add GitHub links to team member list (#1115)

v0.18.1

Sonobuoy v0.18.1

What's new

Sonobuoy now supports plugins providing their own results file in the Sonobuoy metadata format for use in the sonobuoy results workflow. For more details, please see our documentation for this feature.

What's better

• Fixed a bug where Sonobuoy would crash if a pod it was checking was in Waiting state but did not yet have a StartTime.

Changelog

e98209e Prepare v0.18.1 release (#1114)
2a34c45 Add documentation for manual results type (#1112)
4fc098c Add verbose flag when creating kind cluster (#1113)
63f3eba Upgrade to go 1.14 (#1111)
cbc6c0c Upgrade to Kind 0.7.0 (#1110)
423b133 Add a new results format: manual (#1090)
b1016cc Fix crash when running sonobuoy in serverless kubernetes cluster (#1108)

v0.18.0

Sonobuoy v0.18.0

This release corresponds to the Kubernetes v1.18.0 release and introduces support for Kubernetes v1.18.x.

This is our first release to feature initial support for running Sonobuoy on Windows clusters. We have released all the clients and images required to run Sonobuoy on Windows clusters however this feature is still in Beta. For details on running Sonobuoy plugins on Windows nodes and how to create a Windows plugin, please see our example Windows plugin.

What's new

• Added a --kubernetes-version flag to the images subcommand to allow manual specification instead of auto-detection of cluster version.

What's better

• We updated our Code of Conduct.
• Fixed the version of the resource-consumer image used in the 1.13 E2E test images list.
• Removed the deprecated --systemd-logs-flag flag. --systemd-logs-image should be used instead.
• Simplified the installation steps in our documentation.

Changelog

7d97bde Fix missing registry for E2E test image (#1105)
49fa937 Ensure consistent windows image names (#1104)
a4819d2 Ensure all CI steps are run for tags (#1103)
49e3158 Use v1.18.0 kind image (#1102)
9b3d367 Prepare v0.18.0 release (#1101)
7613c7d Simplify installation instructions (#1100)
80987cb Use passed VERSION when generating image manifest (#1099)
0c92eaf Don't error if build directory already exists (#1098)
e915293 Persist images for all targets (#1097)
a8a5459 Remove deprecated --systemd-logs-flag flag (#1096)
0a90d19 Attach workspace before loading docker images (#1093)
e780591 Minor tweak after last commit (#1092)
1965569 Currently in a beta state, we are experimenting with building (#1081)
df6a26b Add kubernetes-version flag to images subcommands (#1085)
6d20c76 Fix 1.13 resource-consumer image tag (#1083)
b1b1358 Change M2 from project to product mgr (#1080)
248e819 Decouple building binaries from images (#1078)
8b6de99 Update Code of Conduct (#1077)

v0.17.2

Release v0.17.2

This is a small release that accomplishes a few things:

• The flag for specifying the image for systemd-logs plugin has been renamed from systemd-logs-flag to systemd-logs-image. The previous flag, systemd-logs-flag, is now deprecated and will be removed in a future release.

• By tagging a new release, fixes an issue that impacted the tip of master and would cause the aggregator pod to exit after plugins completed. This bug only impacted the tip of master and not any of our official releases.

• Includes miscellaneous small patches to clear the way for Windows node support. Users should see no impact.

Changelog

eb9343d Bump version to v0.17.2 and add docs (#1075)
f8c047f Add Sonobuoy plugins page (#1070)
5fd8991 Update to use latest systemd-logs image (#1074)
a49641f Get rid of Linux specific scripts as much as possible (#1072)
c927a9f Use filepath instead of path when possible (#1073)
2f2bb1f Add M2 as a team member on the site (#1069)
7d04c2f Fix flag name for systemd-logs image (#1066)

v0.17.1

Sonobuoy v0.17.1

This release contains numerous small updates which improve the following use-cases:

• airgapped runs
• parallel runs
• custom plugin generation

In addition, messaging was improved in a few locations which should help avoid confusion in common flows, particularly if the API server stops responding temporarily during a run.

What's new

• Added a new flag to sonobuoy gen and sonobuoy run to specify the systemd-logs image.
• Adds two subcommands (e2e and systemd-logs) to sonobuoy gen plugin which will print those plugin definitions respectively. This will hopefully make certain workflows easier by giving users a starting point for their plugin definition.

What's better

• sonobuoy images commands will now pull/tag/push the other images necessary to run Sonobuoy in an airgapped environment: the Sonobuoy image, the E2E test image itself, and the systemd-logs image.
• Fixed an issue where the <error ... > field of JUnit test cases was not parsed. These now get reported via Sonobuoy as failures.
• Fixed a bug which caused daemonset plugins' status to not be updated with results properly.
• Fixed a bug which caused job plugins (like the e2e plugin) to prematurely get marked as failures if the Sonobuoy could not check its status via querying the API server.
• Adds additional metadata into the sonobuoy_results.yaml file to help indicate what each node in the tree represents.
• Added an error message to ensure that users don't set configuration options as well as a --file option when using sonobuoy run.
• Cluster resources are now labeled with the namespace of the Sonobuoy run that created it so that parallel Sonobuoy runs do not delete each others' resources.
• Clarified some error messages which may have mislead users into believing a namespace was not created correctly when it may have been for other reasons.

Changelog

efb9d68 Update goreleaser to remove deprecated field (#1065)
534cb79 Version bump and docs for v0.17.1 (#1063)
23d1d5c Add support for pulling and pushing all images (#1061)
bb0c5a3 Clarify that users shouldn't provide more options when running a file (#1053)
627fa31 Merge pull request #1060 from danielfbm/master
d991dff Bring KIND to 0.6.1 in CircleCI (#1062)
51791ed Merge branch 'master' into master
9c3e4a6 feat: Adding namespace to cluster resources and removing only necessary ones
78b256d Refactor image client to not be E2E specific (#1057)
3f6547e Allow systemd-logs to be configured via CLI
30365d1 Improve error message from GetStatus
e41ac6e Adds commands to print default plugin definitions
be8e183 Tag Items with metadata about the type if item (e.g. node/file/etc)
8f2750f Do not fail jobs if we can't query the API server while running
e0d3921 Remove outdated examples
121ba8d Fix bug which caused daemonset status to not be updated with results
ee12b94 Process JUnit error field
a7a8aa0 Update release docs (#1042)