Sonobuoy

Sonobuoyhttps://sonobuoy.io/docs/v0.57.5/Recent content on SonobuoyHugo -- gohugo.ioen-us<link>https://sonobuoy.io/docs/v0.57.5/aggregator-permissions/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://sonobuoy.io/docs/v0.57.5/aggregator-permissions/</guid><description>Aggregator Permissions By default, the Sonobuoy aggregator is given very elevated permissions in order to successfully run the Kubernetes end-to-end tests. In some situations you may want to (or need to) limit the permissions of the aggregator so that the aggregator and the pods that it creates do not have such wide-reaching permissions. You can always customize the exact permissions of the ServiceAccount via editing sonobuoy gen output manually, but Sonobuoy also provides useful presets via the CLI flag, --aggregator-permissions.</description></item><item><title/><link>https://sonobuoy.io/docs/v0.57.5/airgap/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://sonobuoy.io/docs/v0.57.5/airgap/</guid><description>Custom registries and air-gapped testing In air-gapped deployments where there is no access to the public Docker registries Sonobuoy supports running the end-to-end tests with custom registries. This enables you to test your air-gapped deployment once you’ve loaded the necessary images into a registry that is reachable by your cluster. You will need to make the Sonobuoy image available as well as the images for any plugins you wish to run.</description></item><item><title/><link>https://sonobuoy.io/docs/v0.57.5/cli/sonobuoy/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://sonobuoy.io/docs/v0.57.5/cli/sonobuoy/</guid><description>sonobuoy Generate reports on your Kubernetes cluster by running plugins Synopsis Sonobuoy is a Kubernetes component that generates reports on cluster conformance, configuration, and more sonobuoy [flags] Options -h, --help help for sonobuoy --level level Log level. One of {panic, fatal, error, warn, info, debug, trace} (default info) SEE ALSO sonobuoy delete - Deletes Kubernetes resources that were generated by a Sonobuoy run sonobuoy e2e - Generates a list of all tests and tags in that tests sonobuoy gen - Generates a sonobuoy manifest for submission via kubectl sonobuoy get - Fetches Sonobuoy resources of a specified type sonobuoy images - Manage images used in a plugin to facilitate running them in airgapped (or similar) environments.</description></item><item><title/><link>https://sonobuoy.io/docs/v0.57.5/cli/sonobuoy_delete/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://sonobuoy.io/docs/v0.57.5/cli/sonobuoy_delete/</guid><description>sonobuoy delete Deletes Kubernetes resources that were generated by a Sonobuoy run sonobuoy delete [flags] Options --all In addition to deleting Sonobuoy namespaces, also clean up dangling e2e namespaces (those with 'e2e-framework' and 'e2e-run' labels). --context string Context in the kubeconfig to use. --dry-run If true, only print the image operations that would be performed. -h, --help help for delete --kubeconfig Kubeconfig Path to explicit kubeconfig file. -n, --namespace string The namespace to run Sonobuoy in.</description></item><item><title/><link>https://sonobuoy.io/docs/v0.57.5/cli/sonobuoy_e2e/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://sonobuoy.io/docs/v0.57.5/cli/sonobuoy_e2e/</guid><description>sonobuoy e2e Generates a list of all tests and tags in that tests sonobuoy e2e [flags] Options --context string Context in the kubeconfig to use. -f, --focus string Return tests which match this regular expression -h, --help help for e2e -i, --input string Determines the source of the test lists. Can be [online, offline, -]. If '-' is set, tests will be read from stdin. (default "online") --kubeconfig Kubeconfig Path to explicit kubeconfig file.</description></item><item><title/><link>https://sonobuoy.io/docs/v0.57.5/cli/sonobuoy_gen/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://sonobuoy.io/docs/v0.57.5/cli/sonobuoy_gen/</guid><description>sonobuoy gen Generates a sonobuoy manifest for submission via kubectl sonobuoy gen [flags] Options --aggregator-node-selector nodeSelectors Node selectors to add to the aggregator. Values can be given multiple times and are in the form key:value (default map[]) --aggregator-permissions string Type of aggregator permission to use in the cluster. Allowable values are [namespaceAdmin, clusterRead, clusterAdmin] (default "clusterAdmin") --config Sonobuoy config Path to a sonobuoy configuration JSON file. --context string Context in the kubeconfig to use.</description></item><item><title/><link>https://sonobuoy.io/docs/v0.57.5/cli/sonobuoy_gen_config/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://sonobuoy.io/docs/v0.57.5/cli/sonobuoy_gen_config/</guid><description>sonobuoy gen config Generates a Sonobuoy config for input to sonobuoy gen or run. sonobuoy gen config [flags] Options --aggregator-node-selector nodeSelectors Node selectors to add to the aggregator. Values can be given multiple times and are in the form key:value (default map[]) --aggregator-permissions string Type of aggregator permission to use in the cluster. Allowable values are [namespaceAdmin, clusterRead, clusterAdmin] (default "clusterAdmin") --config Sonobuoy config Path to a sonobuoy configuration JSON file.</description></item><item><title/><link>https://sonobuoy.io/docs/v0.57.5/cli/sonobuoy_gen_default-image-config/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://sonobuoy.io/docs/v0.57.5/cli/sonobuoy_gen_default-image-config/</guid><description>sonobuoy gen default-image-config Generates the default image registry config for the e2e plugin sonobuoy gen default-image-config [flags] Options --context string Context in the kubeconfig to use. -h, --help help for default-image-config --kubeconfig Kubeconfig Path to explicit kubeconfig file. Options inherited from parent commands --level level Log level. One of {panic, fatal, error, warn, info, debug, trace} (default info) SEE ALSO sonobuoy gen - Generates a sonobuoy manifest for submission via kubectl Auto generated by spf13/cobra on 1-Jul-2026</description></item><item><title/><link>https://sonobuoy.io/docs/v0.57.5/cli/sonobuoy_gen_plugin/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://sonobuoy.io/docs/v0.57.5/cli/sonobuoy_gen_plugin/</guid><description>sonobuoy gen plugin Generates the manifest Sonobuoy uses to define a plugin sonobuoy gen plugin [flags] Examples sonobuoy gen plugin -n myPlugin -i myregistry/myimage:v0 Options -a, --arg stringArray Arg values to set on the plugin. Can be set multiple times (e.g. --arg 'arg 1' --arg arg2) -c, --cmd stringArray Command to run when starting the plugin's container. Can be set multiple times (e.g. --cmd /bin/sh -c "-c") (default [./run.sh]) --configmap stringArray Specifies files to read and add as configMaps.</description></item><item><title/><link>https://sonobuoy.io/docs/v0.57.5/cli/sonobuoy_gen_plugin_e2e/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://sonobuoy.io/docs/v0.57.5/cli/sonobuoy_gen_plugin_e2e/</guid><description>sonobuoy gen plugin e2e Generates the e2e plugin definition based on the given options sonobuoy gen plugin e2e [flags] Options --aggregator-node-selector nodeSelectors Node selectors to add to the aggregator. Values can be given multiple times and are in the form key:value (default map[]) --aggregator-permissions string Type of aggregator permission to use in the cluster. Allowable values are [namespaceAdmin, clusterRead, clusterAdmin] (default "clusterAdmin") --config Sonobuoy config Path to a sonobuoy configuration JSON file.</description></item><item><title/><link>https://sonobuoy.io/docs/v0.57.5/cli/sonobuoy_gen_plugin_systemd-logs/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://sonobuoy.io/docs/v0.57.5/cli/sonobuoy_gen_plugin_systemd-logs/</guid><description>sonobuoy gen plugin systemd-logs Generates the systemd-logs plugin definition based on the given options sonobuoy gen plugin systemd-logs [flags] Options --aggregator-node-selector nodeSelectors Node selectors to add to the aggregator. Values can be given multiple times and are in the form key:value (default map[]) --aggregator-permissions string Type of aggregator permission to use in the cluster. Allowable values are [namespaceAdmin, clusterRead, clusterAdmin] (default "clusterAdmin") --config Sonobuoy config Path to a sonobuoy configuration JSON file.</description></item><item><title/><link>https://sonobuoy.io/docs/v0.57.5/cli/sonobuoy_get/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://sonobuoy.io/docs/v0.57.5/cli/sonobuoy_get/</guid><description>sonobuoy get Fetches Sonobuoy resources of a specified type Options -h, --help help for get Options inherited from parent commands --level level Log level. One of {panic, fatal, error, warn, info, debug, trace} (default info) SEE ALSO sonobuoy - Generate reports on your Kubernetes cluster by running plugins sonobuoy get pod - Fetch sonobuoy pods Auto generated by spf13/cobra on 1-Jul-2026</description></item><item><title/><link>https://sonobuoy.io/docs/v0.57.5/cli/sonobuoy_get_pod/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://sonobuoy.io/docs/v0.57.5/cli/sonobuoy_get_pod/</guid><description>sonobuoy get pod Fetch sonobuoy pods sonobuoy get pod [flags] Options -h, --help help for pod -n, --namespace string The namespace to run Sonobuoy in. Only one Sonobuoy run can exist per namespace simultaneously. (default "sonobuoy") -p, --plugin string Plugin to locate pods for Options inherited from parent commands --level level Log level. One of {panic, fatal, error, warn, info, debug, trace} (default info) SEE ALSO sonobuoy get - Fetches Sonobuoy resources of a specified type Auto generated by spf13/cobra on 1-Jul-2026</description></item><item><title/><link>https://sonobuoy.io/docs/v0.57.5/cli/sonobuoy_images/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://sonobuoy.io/docs/v0.57.5/cli/sonobuoy_images/</guid><description>sonobuoy images Manage images used in a plugin to facilitate running them in airgapped (or similar) environments. Supported plugins are: ‘e2e’ sonobuoy images [flags] Options --context string Context in the kubeconfig to use. --dry-run If true, only print the image operations that would be performed. -h, --help help for images --kubeconfig Kubeconfig Path to explicit kubeconfig file. --kubernetes-version string Use default E2E image, but override the version. Default is 'auto', which will be set to your cluster's version if detected, erroring otherwise.</description></item><item><title/><link>https://sonobuoy.io/docs/v0.57.5/cli/sonobuoy_images_delete/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://sonobuoy.io/docs/v0.57.5/cli/sonobuoy_images_delete/</guid><description>sonobuoy images delete Deletes all images downloaded to local docker client sonobuoy images delete [flags] Options --context string Context in the kubeconfig to use. --dry-run If true, only print the image operations that would be performed. --e2e-repo string Specify a registry for KUBE_TEST_REPO, overriding registries for test images. --e2e-repo-config string Specify a yaml file acting as KUBE_TEST_REPO_LIST, overriding registries for test images. -h, --help help for delete --kubeconfig Kubeconfig Path to explicit kubeconfig file.</description></item><item><title/><link>https://sonobuoy.io/docs/v0.57.5/cli/sonobuoy_images_download/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://sonobuoy.io/docs/v0.57.5/cli/sonobuoy_images_download/</guid><description>sonobuoy images download Saves downloaded images from local docker client to a tar file sonobuoy images download [flags] Options --context string Context in the kubeconfig to use. --dry-run If true, only print the image operations that would be performed. --e2e-repo string Specify a registry for KUBE_TEST_REPO, overriding registries for test images. --e2e-repo-config string Specify a yaml file acting as KUBE_TEST_REPO_LIST, overriding registries for test images. -h, --help help for download --kubeconfig Kubeconfig Path to explicit kubeconfig file.</description></item><item><title/><link>https://sonobuoy.io/docs/v0.57.5/cli/sonobuoy_images_inspect/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://sonobuoy.io/docs/v0.57.5/cli/sonobuoy_images_inspect/</guid><description>sonobuoy images inspect Inspect images Synopsis Inspect if image is available in the registry sonobuoy images inspect [flags] Options --context string Context in the kubeconfig to use. --dry-run If true, only print the image operations that would be performed. -h, --help help for inspect --kubeconfig Kubeconfig Path to explicit kubeconfig file. --kubernetes-version string Use default E2E image, but override the version. Default is 'auto', which will be set to your cluster's version if detected, erroring otherwise.</description></item><item><title/><link>https://sonobuoy.io/docs/v0.57.5/cli/sonobuoy_images_list/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://sonobuoy.io/docs/v0.57.5/cli/sonobuoy_images_list/</guid><description>sonobuoy images list List images sonobuoy images list [flags] Options --context string Context in the kubeconfig to use. --dry-run If true, only print the image operations that would be performed. -h, --help help for list --kubeconfig Kubeconfig Path to explicit kubeconfig file. --kubernetes-version string Use default E2E image, but override the version. Default is 'auto', which will be set to your cluster's version if detected, erroring otherwise. 'ignore' will try version resolution but ignore errors.</description></item><item><title/><link>https://sonobuoy.io/docs/v0.57.5/cli/sonobuoy_images_pull/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://sonobuoy.io/docs/v0.57.5/cli/sonobuoy_images_pull/</guid><description>sonobuoy images pull Pulls images to local docker client for a specific plugin sonobuoy images pull [flags] Options --context string Context in the kubeconfig to use. --dry-run If true, only print the image operations that would be performed. --e2e-repo string Specify a registry for KUBE_TEST_REPO, overriding registries for test images. --e2e-repo-config string Specify a yaml file acting as KUBE_TEST_REPO_LIST, overriding registries for test images. -h, --help help for pull --kubeconfig Kubeconfig Path to explicit kubeconfig file.</description></item><item><title/><link>https://sonobuoy.io/docs/v0.57.5/cli/sonobuoy_images_push/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://sonobuoy.io/docs/v0.57.5/cli/sonobuoy_images_push/</guid><description>sonobuoy images push Pushes images to docker registry for a specific plugin sonobuoy images push [flags] Options --context string Context in the kubeconfig to use. --custom-registry string Specify a registry to override the Sonobuoy and Plugin image registries. --dry-run If true, only print the image operations that would be performed. --e2e-repo string Specify a registry for KUBE_TEST_REPO, overriding registries for test images. --e2e-repo-config string Specify a yaml file acting as KUBE_TEST_REPO_LIST, overriding registries for test images.</description></item><item><title/><link>https://sonobuoy.io/docs/v0.57.5/cli/sonobuoy_logs/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://sonobuoy.io/docs/v0.57.5/cli/sonobuoy_logs/</guid><description>sonobuoy logs Dumps the logs of the currently running Sonobuoy containers for diagnostics sonobuoy logs [flags] Options --context string Context in the kubeconfig to use. -f, --follow Continue following the logs of the Sonobuoy created containers. -h, --help help for logs --kubeconfig Kubeconfig Path to explicit kubeconfig file. -n, --namespace string The namespace to run Sonobuoy in. Only one Sonobuoy run can exist per namespace simultaneously. (default "sonobuoy") -p, --plugin string Show logs only for a specific plugin.</description></item><item><title/><link>https://sonobuoy.io/docs/v0.57.5/cli/sonobuoy_modes/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://sonobuoy.io/docs/v0.57.5/cli/sonobuoy_modes/</guid><description>sonobuoy modes Display the various modes in which to run the e2e plugin sonobuoy modes [flags] Options -h, --help help for modes --verbose Do not truncate output for each mode. Options inherited from parent commands --level level Log level. One of {panic, fatal, error, warn, info, debug, trace} (default info) SEE ALSO sonobuoy - Generate reports on your Kubernetes cluster by running plugins Auto generated by spf13/cobra on 1-Jul-2026</description></item><item><title/><link>https://sonobuoy.io/docs/v0.57.5/cli/sonobuoy_plugin/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://sonobuoy.io/docs/v0.57.5/cli/sonobuoy_plugin/</guid><description>sonobuoy plugin Manage your installed plugins Options -h, --help help for plugin Options inherited from parent commands --level level Log level. One of {panic, fatal, error, warn, info, debug, trace} (default info) SEE ALSO sonobuoy - Generate reports on your Kubernetes cluster by running plugins sonobuoy plugin install - Install a plugin so that it can be run via just its filename rather than a full path or URL.</description></item><item><title/><link>https://sonobuoy.io/docs/v0.57.5/cli/sonobuoy_plugin_install/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://sonobuoy.io/docs/v0.57.5/cli/sonobuoy_plugin_install/</guid><description>sonobuoy plugin install Install a plugin so that it can be run via just its filename rather than a full path or URL. sonobuoy plugin install <save-as-filename> <source filename or URL> [flags] Options -h, --help help for install Options inherited from parent commands --level level Log level. One of {panic, fatal, error, warn, info, debug, trace} (default info) SEE ALSO sonobuoy plugin - Manage your installed plugins Auto generated by spf13/cobra on 1-Jul-2026</description></item><item><title/><link>https://sonobuoy.io/docs/v0.57.5/cli/sonobuoy_plugin_list/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://sonobuoy.io/docs/v0.57.5/cli/sonobuoy_plugin_list/</guid><description>sonobuoy plugin list List all installed plugins sonobuoy plugin list [flags] Options -h, --help help for list Options inherited from parent commands --level level Log level. One of {panic, fatal, error, warn, info, debug, trace} (default info) SEE ALSO sonobuoy plugin - Manage your installed plugins Auto generated by spf13/cobra on 1-Jul-2026</description></item><item><title/><link>https://sonobuoy.io/docs/v0.57.5/cli/sonobuoy_plugin_show/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://sonobuoy.io/docs/v0.57.5/cli/sonobuoy_plugin_show/</guid><description>sonobuoy plugin show Print the full definition of the named plugin file sonobuoy plugin show <plugin filename> [flags] Options -h, --help help for show Options inherited from parent commands --level level Log level. One of {panic, fatal, error, warn, info, debug, trace} (default info) SEE ALSO sonobuoy plugin - Manage your installed plugins Auto generated by spf13/cobra on 1-Jul-2026</description></item><item><title/><link>https://sonobuoy.io/docs/v0.57.5/cli/sonobuoy_plugin_uninstall/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://sonobuoy.io/docs/v0.57.5/cli/sonobuoy_plugin_uninstall/</guid><description>sonobuoy plugin uninstall Uninstall a plugin. You can continue to run any plugin via specifying a file or URL. sonobuoy plugin uninstall <plugin filename> [flags] Options -h, --help help for uninstall Options inherited from parent commands --level level Log level. One of {panic, fatal, error, warn, info, debug, trace} (default info) SEE ALSO sonobuoy plugin - Manage your installed plugins Auto generated by spf13/cobra on 1-Jul-2026</description></item><item><title/><link>https://sonobuoy.io/docs/v0.57.5/cli/sonobuoy_query/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://sonobuoy.io/docs/v0.57.5/cli/sonobuoy_query/</guid><description>sonobuoy query Runs queries against your cluster in order to aid in debugging. sonobuoy query [flags] Options --config Sonobuoy config Path to a sonobuoy configuration JSON file. -h, --help help for query -o, --output string Directory to output results into. If empty, will default to a UUID folder in the pwd. Options inherited from parent commands --level level Log level. One of {panic, fatal, error, warn, info, debug, trace} (default info) SEE ALSO sonobuoy - Generate reports on your Kubernetes cluster by running plugins Auto generated by spf13/cobra on 1-Jul-2026</description></item><item><title/><link>https://sonobuoy.io/docs/v0.57.5/cli/sonobuoy_results/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://sonobuoy.io/docs/v0.57.5/cli/sonobuoy_results/</guid><description>sonobuoy results Inspect plugin results. sonobuoy results archive.tar.gz [flags] Options -h, --help help for results -m, --mode string Modifies the format of the output. Valid options are report, detailed, readable, or dump. (default "report") -n, --node string Traverse results starting at the node with the given name. Defaults to the real root. -p, --plugin string Which plugin to show results for. Defaults to printing them all. -s, --skip-prefix When printing items linking to files, only print the file contents.</description></item><item><title/><link>https://sonobuoy.io/docs/v0.57.5/cli/sonobuoy_retrieve/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://sonobuoy.io/docs/v0.57.5/cli/sonobuoy_retrieve/</guid><description>sonobuoy retrieve Retrieves the results of a sonobuoy run to a specified path sonobuoy retrieve [path] [flags] Options --context string Context in the kubeconfig to use. -x, --extract If true, extracts the results instead of just downloading the results tarball. -f, --filename string Specify the name of the downloaded file. If empty, defaults to the name of the tarball in the pod. -h, --help help for retrieve --kubeconfig Kubeconfig Path to explicit kubeconfig file.</description></item><item><title/><link>https://sonobuoy.io/docs/v0.57.5/cli/sonobuoy_run/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://sonobuoy.io/docs/v0.57.5/cli/sonobuoy_run/</guid><description>sonobuoy run Starts a Sonobuoy run by launching the Sonobuoy aggregator and plugin pods. sonobuoy run [flags] Options --aggregator-node-selector nodeSelectors Node selectors to add to the aggregator. Values can be given multiple times and are in the form key:value (default map[]) --aggregator-permissions string Type of aggregator permission to use in the cluster. Allowable values are [namespaceAdmin, clusterRead, clusterAdmin] (default "clusterAdmin") --config Sonobuoy config Path to a sonobuoy configuration JSON file.</description></item><item><title/><link>https://sonobuoy.io/docs/v0.57.5/cli/sonobuoy_status/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://sonobuoy.io/docs/v0.57.5/cli/sonobuoy_status/</guid><description>sonobuoy status Gets a summarized status of a sonobuoy run sonobuoy status [flags] Options --context string Context in the kubeconfig to use. -h, --help help for status --json Print the status object as json --kubeconfig Kubeconfig Path to explicit kubeconfig file. -n, --namespace string The namespace to run Sonobuoy in. Only one Sonobuoy run can exist per namespace simultaneously. (default "sonobuoy") --show-all Don't summarize plugin statuses, show results for each node Options inherited from parent commands --level level Log level.</description></item><item><title/><link>https://sonobuoy.io/docs/v0.57.5/cli/sonobuoy_version/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://sonobuoy.io/docs/v0.57.5/cli/sonobuoy_version/</guid><description>sonobuoy version Print sonobuoy version sonobuoy version [flags] Options --context string Context in the kubeconfig to use. -h, --help help for version --kubeconfig Kubeconfig Path to explicit kubeconfig file. --short If true, prints just the Sonobuoy version. Options inherited from parent commands --level level Log level. One of {panic, fatal, error, warn, info, debug, trace} (default info) SEE ALSO sonobuoy - Generate reports on your Kubernetes cluster by running plugins Auto generated by spf13/cobra on 1-Jul-2026</description></item><item><title/><link>https://sonobuoy.io/docs/v0.57.5/cli/sonobuoy_wait/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://sonobuoy.io/docs/v0.57.5/cli/sonobuoy_wait/</guid><description>sonobuoy wait Waits on the Sonobuoy run in the targeted namespace. sonobuoy wait [flags] Options --aggregator-node-selector nodeSelectors Node selectors to add to the aggregator. Values can be given multiple times and are in the form key:value (default map[]) --aggregator-permissions string Type of aggregator permission to use in the cluster. Allowable values are [namespaceAdmin, clusterRead, clusterAdmin] (default "clusterAdmin") --config Sonobuoy config Path to a sonobuoy configuration JSON file. --context string Context in the kubeconfig to use.</description></item><item><title/><link>https://sonobuoy.io/docs/v0.57.5/dryrun-listgenerator/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://sonobuoy.io/docs/v0.57.5/dryrun-listgenerator/</guid><description>Plugins used to help create test lists This process has been dramatically simplified. All that is necessary is that you create a new Git branch/PR and run ./scripts/gather_e2e_data.sh and commit the changes. You can look through the script and the supporting files for a more in depth explanation of the process but it just boils down to finding the proper versions to check, running them in DRY_RUN mode, and extracting the necessary data.</description></item><item><title/><link>https://sonobuoy.io/docs/v0.57.5/e2eplugin/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://sonobuoy.io/docs/v0.57.5/e2eplugin/</guid><description>The Kubernetes End-To-End Testing Plugin The Kubernetes end-to-end testing plugin (the e2e plugin) is used to run tests which are maintained by the upstream Kubernetes community in the kubernetes/kubernetes repo. There are numerous ways to run this plugin in order to meet your testing needs. Choosing Which Tests To Run The most common point of customization is changing the set of tests to run. This is controlled by two environment variables the test image recognizes:</description></item><item><title/><link>https://sonobuoy.io/docs/v0.57.5/faq/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://sonobuoy.io/docs/v0.57.5/faq/</guid><description>Frequently Asked Questions Kubernetes Conformance and end-to-end testing Why were so many tests skipped? When running the e2e plugin on Sonobuoy, you will notice that a large number of tests are skipped by default. The reason for this is that the image used by Sonobuoy to run the Kubernetes conformance tests contains all the end-to-end tests for Kubernetes. However, only a subset of those tests are required to check conformance. For example, the v1.</description></item><item><title/><link>https://sonobuoy.io/docs/v0.57.5/gen/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://sonobuoy.io/docs/v0.57.5/gen/</guid><description>Customization Sonobuoy provides many flags to customize your run but sometimes you have a special use case that isn’t supported yet. For these cases, Sonobuoy provides sonobuoy gen. The command sonobuoy gen will print the YAML for your run to stdout instead of actually creating it. It accepts all of the relevant flags for customizing the run just like sonobuoy run would. You can then edit it yourself and apply it as if Sonobuoy had run it.</description></item><item><title/><link>https://sonobuoy.io/docs/v0.57.5/img/readme/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://sonobuoy.io/docs/v0.57.5/img/readme/</guid><description>Some of these diagrams (for instance sonobuoy-plugins.png), have been created on draw.io, using the “Include a copy of my diagram” option. If you want to make changes to these diagrams, try importing them into draw.io, and you should have access to the original shapes/text that went into the originals.</description></item><item><title/><link>https://sonobuoy.io/docs/v0.57.5/issue1388/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://sonobuoy.io/docs/v0.57.5/issue1388/</guid><description>Issue Regarding Certified-Conformance Mode Versions of Sonobuoy Impacted v0.53.0 v0.53.1 Description When running sonobuoy run --mode=certified-conformance the E2E_SKIP value is not properly cleared, leading to disruptive tests being skipped. In certified-conformance mode, all tests must be run to be valid for submission to the CNCF so this bug would invalidate your results. Work-around #1 You can manually work-around this issue by adding an extra flag at the end of your command:</description></item><item><title/><link>https://sonobuoy.io/docs/v0.57.5/plugins/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://sonobuoy.io/docs/v0.57.5/plugins/</guid><description>Sonobuoy Plugins Overview The main function of Sonobuoy is running plugins; each plugin may run tests or gather data in the cluster. When you first run Sonobuoy, an aggregator pod is created in the cluster which reads the configuration you’ve chosen and launches each plugin. The aggregator then waits for each plugin to report results back to it. If the plugin fails to launch correctly or does not report results within the timeout period, an error is recorded.</description></item><item><title/><link>https://sonobuoy.io/docs/v0.57.5/pullsecrets/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://sonobuoy.io/docs/v0.57.5/pullsecrets/</guid><description>Using a Private Sonobuoy Image with ImagePullSecrets This document describes how to use the ImagePullSecrets option in order to run Sonobuoy using a private Sonobuoy image. Setting ImagePullSecrets The name of the secret to use when pulling the image can be set easily in the configuration file passed to sonobuoy run or sonobuoy gen: echo '{"ImagePullSecrets":"mysecret"}' > secretconfig.json sonobuoy gen --config secretconfig.json Doing this properly passes the value and places it into the YAML for the Sonobuoy aggregator pod and all the pods for each plugin.</description></item><item><title/><link>https://sonobuoy.io/docs/v0.57.5/release/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://sonobuoy.io/docs/v0.57.5/release/</guid><description>Release Preparing release version Update the version defined in the code to the new version number. As of the time of writing, the version is defined in pkg/buildinfo/version.go. Kubernetes release Is there a Kubernetes release since the last Sonobuoy release? If so, apply the following steps: Conformance images Ensure the upstream conformance script is working appropriately: Update the kind-config.yaml file with the new image version here. Run conformance tests Updating the versioned docs Explicit doc changes (if any) should be made to the appropriate files in directory site/docs/main.</description></item><item><title/><link>https://sonobuoy.io/docs/v0.57.5/results/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://sonobuoy.io/docs/v0.57.5/results/</guid><description>Viewing Plugin Results The sonobuoy results command can be used to print the results of a plugin without first having to extract the files from the tarball. Canonical Data Format Plugin results undergo post-processing on the server to produce a tree-like file which contains information about the tests run (or files generated) by the plugin. This is the file which enables sonobuoy results to present reports to the user and navigate the tarball effectively.</description></item><item><title/><link>https://sonobuoy.io/docs/v0.57.5/snapshot/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://sonobuoy.io/docs/v0.57.5/snapshot/</guid><description>Sonobuoy Snapshot Layout Retrieving results Filename Contents /hosts /meta /plugins /podlogs /resources /servergroups.json /serverversion.json This document describes retrieving the Sonobuoy results tarball, its layout, how it is formatted, and how data is named and laid out. Retrieving results To view the output, copy the output directory from the aggregator Sonobuoy pod to your local machine (and save the name of the file to a variable for reference):</description></item><item><title/><link>https://sonobuoy.io/docs/v0.57.5/sonobuoy-config/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://sonobuoy.io/docs/v0.57.5/sonobuoy-config/</guid><description>Sonobuoy Config The commands “run” and “gen” both accept a parameter for a Sonobuoy config file which allows you to customize multiple aspects of the run. We’ve provided a command to generate the JSON file necessary so that it is easier to edit for your runs. Run the command: sonobuoy gen config and you will see the default configuration. Below is a description of each of the values. General options Description: A string which provides consumers a way to add extra context to a configuration that may be in memory or saved to disk.</description></item><item><title/><link>https://sonobuoy.io/docs/v0.57.5/sonobuoy-query/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://sonobuoy.io/docs/v0.57.5/sonobuoy-query/</guid><description>sonobuoy query command Intro sonobuoy query command runs queries against your cluster and helps in debugging by providing useful information about the cluster which helps us to find bugs and fix them before they can cause any severe harm to the cluster. These queries were run from the aggregator pod (made through sonobuoy run) in the past. Now you can run them locally without running Sonobuoy or launching pods. Just run sonobuoy query which is much faster and convenient.</description></item><item><title/><link>https://sonobuoy.io/docs/v0.57.5/strategy/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://sonobuoy.io/docs/v0.57.5/strategy/</guid><description>Sonobuoy Strategy The problem Users of Kubernetes value its ability to automate running complex systems at scale. However, little Kubernetes cluster validation is automated. As a result, skilled Kubernetes operators spend needless time performing manual tasks. Just as automated unit tests frontload the work of testing software by having the developer codify how to check that their code is functional, Kubernetes would benefit from automated test suites that allow skilled Kubernetes operators and developers to codify once how to test cluster capabilities and then have those checks run by whichever Kubernetes user needs this.</description></item></channel></rss>