-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade sonobuoy to v0.51 #557
Comments
Patchset https://review.opendev.org/c/airship/airshipctl/+/782614 |
I will take the issue. Thank you :) |
Just a quick update. We used 0.51 coz that got released at the time of testing. :) |
* adjust kubebench conformance scripts to use ~/.airship/kubeconfig * adjust sonobuoy conformance scripts to use ~/.airship/kubeconfig * update sonobuoy version to 0.51 Relates-To: #557 Change-Id: I5c300e6740f0d050c0619473934af6f4d3b48816
This can be closed. The patchset for it got merged.https://review.opendev.org/c/airship/airshipctl/+/782614 |
Closing per above |
To provide additional automated testing support for Airship 2, we need to upgrade Sonobuoy from v0.18.2 to v0.51.
From the Sonobuoy release notes, this is an incremental release, but utilizes a new release numbering schema.
https://sonobuoy.io/sonobuoy-v0-50/
Previously the Sonobuoy version number was coupled with the Kubernetes release number. As part of the march toward version v1.0, we decided to break that incremental versioning scheme and decouple our releases from that of Kubernetes release cadence. To amplify this effort, we have decided to reset our release number scheme going from v0.20 to v0.51 to ensure that there is no perceived relation between a Sonobuoy release and a Kubernetes release. This is because all Sonobuoy binaries will support most Kubernetes releases.
The text was updated successfully, but these errors were encountered: