Sonobuoy is a diagnostic tool that makes it easier to understand the state of a Kubernetes cluster by running a set of plugins (including Kubernetes conformance tests) in an accessible and non-destructive manner. It is a customizable, extendable, and cluster-agnostic way to generate clear, informative reports about your cluster.
Its selective data dumps of Kubernetes resource objects and cluster nodes allow for the following use cases:
- Integrated end-to-end (e2e) conformance-testing
- Workload debugging
- Custom data collection via extensible plugins
Sonobuoy supports 3 Kubernetes minor versions: the current release and 2 minor versions before. Sonobuoy is currently versioned to track the Kubernetes minor version to clarify the support matrix. For example, Sonobuoy v0.14.x would support Kubernetes 1.14.x, 1.13.x, and 1.12.x.
Note: You can skip this version enforcement by running Sonobuoy with the
--skip-preflightflag.
-
Access to an up-and-running Kubernetes cluster. If you do not have a cluster, we recommend following the AWS Quickstart for Kubernetes instructions.
-
An admin
kubeconfigfile, and the KUBECONFIG environment variable set. -
For some advanced workflows it may be required to have
kubectlinstalled. See installing via Homebrew (MacOS) or building the binary (Linux). -
The
sonobuoy imagessubcommand requires Docker to be installed. See installing Docker.
Download one of the releases directly from here.
Alternatively, you can install the CLI by running:
go get -u -v github.com/heptio/sonobuoyGolang version 1.12 or greater is recommended. Golang can be installed via gimme.
To launch conformance tests (ensuring CNCF conformance) and wait until they are finished run:
sonobuoy run --waitNote: Using
--mode quickwill significantly shorten the runtime of Sonobuoy. It runs just a single test, helping to quickly validate your Sonobuoy and Kubernetes configuration.
Get the results from the plugins (e.g. e2e test results):
results=$(sonobuoy retrieve)Inspect results for test failures. This will list the number of tests failed and their names:
sonobuoy e2e $resultsYou can also extract the entire contents of the file to get much more detailed data about your cluster.
Sonobuoy creates a few resources in order to run and expects to run within its own namespace.
Deleting Sonobuoy entails removing it's namespace as well as a few cluster scoped resources.
sonobuoy delete --waitNote: The --wait option ensures the Kubernetes namespace is deleted, avoiding conflicts if another Sonobuoy run is started quickly.
You can check on the status of each of the plugins running with:
sonobuoy statusYou can also inspect the logs of all Sonobuoy containers:
sonobuoy logsThe documentation provides further information about:
- conformance tests
- plugins
- Testing of air gapped clusters.
- Customization of YAML prior to running.
- The Sonobuoy config file file and how to edit it.
If you encounter any problems that the documentation does not address, file an issue.
There are some Kubernetes e2e tests that may leak resources. Sonobuoy can
help clean those up as well by deleting all namespaces prefixed with e2e:
sonobuoy delete --allSonobuoy requires admin permissions which won't be automatic if you are running via Google Kubernetes Engine (GKE) cluster. You must first create an admin role for the user under which you run Sonobuoy:
kubectl create clusterrolebinding <your-user-cluster-admin-binding> --clusterrole=cluster-admin --user=<[email protected]>Thanks for taking the time to join our community and start contributing! We welcome pull requests. Feel free to dig through the issues and jump in.
- Please familiarize yourself with the Code of Conduct before contributing.
- See CONTRIBUTING.md for instructions on the developer certificate of origin that we require.
- There is a Slack channel if you want to interact with other members of the community
See the list of releases to find out about feature changes.