-
Notifications
You must be signed in to change notification settings - Fork 344
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
Are you using Sonobuoy? We want to hear from you! #669
Comments
My company has been using it in an ad-hoc manner to test new K8s releases with our bootstrapping to help verify that everything still runs as expected. We are looking to automate this in the future so that a new release automatically spins up a cluster, runs a series of tests (including conformance) and outputs the results in a consistent and friendly manner. I hope that helps and is what you are looking for. Thanks for reaching out to the community! |
@johnSchnake I am evaluating this repo to see if we can run the kube-bench plugin. |
|
how to run only a specific test? |
@ashutoshishere04 You use the See https://sonobuoy.io/docs/v0.16.0/results/ for how to see results in various ways. Just based on the timing of this question, I would also like to point you towards #910 which found a problem with the k/k testing image which caused it to not save results (and report them to Sonobuoy) when a test error was encountered (on v1.16.0 test image). Our release of Sonobuoy v0.16.1 today should mitigate that problem though. |
@johnSchnake Thanks it saved a lot of my time(not running all cases again for one case's result), |
@ashutoshishere04 You'll have to look into the exact logs to determine that; I'm not familiar with all the different error modes for these tests. However, the commit you linked to was committed into Kubernetes v1.7.0 so it is a part of the code paths you're using for v1.12.8. |
Team, |
k3s is using Sonobuoy for running the conformance tests on every PR, and we try to minimize the runtime as much as possible. To achieve this we create two virtual clusters, one to run the serial portion of the conformance tests, and the other to run the parallel portion of the conformance tests. This allows us to test the full conformance suite in about 20 minutes on multiple architectures (currently amd64 & arm64). We would also like to enable testing for arm but probably need lots of supporting images to be created. We have also disabled syslog support and enabled the e2e go runner. For reference how we are separating the serial and parallel portion: And how we are launching sonobuoy itself: Thanks for an awesome utility! |
There has not been much activity here. We'll be closing this issue if there are no follow-ups within 15 days. |
Stalebot! Just talking about how I thought this issue existed on #1371 We wanted to reopen this so people can record where/how they use Sonobuoy to help share workflows/plugins etc in a very informal way. |
We use Sonobuoy to implement the Crossplane CNCF conformance suite per https://github.com/crossplane/conformance and https://github.com/cncf/crossplane-conformance. |
In Rancher, we use Sonobuoy to invoke Reference: https://github.com/rancher/security-scan/blob/master/package/run.sh |
Hi John, The following is long overdue but I have published last year a paper about comparing K8-as-a-Service vendors based on analysis of various information sources, one of which are results of the end2end conformance testing suite of Kubernetes. I've written some code for automating the comparison based on the e2e results (extracted from It does the following steps:
As you can see, my code does similar things as sonobuoy results. It is possible to aggregate results from multiple tar balls from multiple vendors and the main output is a Summary.csv file. Each entry in the csv corresponds with a documented k8s feature, a specific set of e2e test regular expressions that relate to that k8s feature, and per vendor the number of succeeded and failed tests. For each vendor there are two other files with the same structure as Summary.csv. "vendor_fail.csv" en "vendor_success.csv". Each entry contains the snippets of the junit file that correspond with the selected tests. I am now starting a new project based on this work and I did a very small test of my code for output of [Kubernetes-conformance image19.4, sonobuoy 0.52.3]. It still seems to work. However it contains some hacky Maybe my code is usable in some sense. Do you know of related projects? Below you find the references
Don't hesitate to contact me in case you have questions, Best regards, Eddy |
@eddytruyen I think the paper link should be https://ieeexplore.ieee.org/document/9298825 Thanks so much for your submission, I'm definitely going to take some time to read through. Sounds great though :) Update: I just wanted to comment a few things for visibility for people looking at the paper/our comments later.
I'm so thrilled that we were of use in your analysis. Thank you for sharing this with us all! |
I've been looking at sonobuoy to replace our home grown tools for running k8s e2e tests. So far it looks like a huge improvement. My favorite feature so far the ability to easily re-run just the e2e tests which failed previously. One usability nit I can see is that if you are using air gapped clusters (or gatekeeper), you have to specify command line flags to point to various config which will map the location to pull the sonobuoy image as well as the images used by the e2e tests themselves. While this will obviously work, it would be nice if sonobuoy would also look for config in some default location like say |
Thanks for the feedback! We just introduced that location as the home for plugins so it does open the gates for ideas/use cases like this. 👍 @matthias50 |
There has not been much activity here. We'll be closing this issue if there are no follow-ups within 15 days. |
We would love to know about your use of Sonobuoy. Share anything Sonobuoy related:
Why?
Tracking usage in OSS is hard, if you leave a comment on this issue we can better understand who our users are and deliver a better experience for YOU!
How you can help
Submit a comment in this issue to include the following information:
The text was updated successfully, but these errors were encountered: