<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Blog on Sonobuoy</title><link>https://sonobuoy.io/blog/</link><description>Recent content in Blog on Sonobuoy</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Fri, 01 Jul 2022 00:00:00 +0000</lastBuildDate><atom:link href="https://sonobuoy.io/blog/feed.xml" rel="self" type="application/rss+xml"/><item><title>July Drumbeat</title><link>https://sonobuoy.io/july-drumbeat/</link><pubDate>Fri, 01 Jul 2022 00:00:00 +0000</pubDate><guid>https://sonobuoy.io/july-drumbeat/</guid><description>Sonobuoy Drumbeat Now that we release on a fairly frequent basis (every 1-3 weeks) we like to present a summary of relevant changes periodically for users updating Sonobuoy.
Dealing with encoded newlines and tabs in results When running sonobuoy results &amp;lt;tarball&amp;gt; --mode dump you get the full results of the plugins in a YAML format. The problem is that often, newlines and tabs are encoded as &amp;ldquo;\n&amp;rdquo; and &amp;ldquo;\t&amp;rdquo; making it very difficult to read large blocks of text.</description></item><item><title>April Drumbeat: Better Output, Faster Debugging, and More Plugins</title><link>https://sonobuoy.io/april-drumbeat/</link><pubDate>Thu, 07 Apr 2022 00:00:00 +0000</pubDate><guid>https://sonobuoy.io/april-drumbeat/</guid><description>Sonobuoy Drumbeat We’ve recently switched to releasing Sonobuoy in more rapid, smaller releases and so we wanted to take an opportunity to discuss recent changes more in depth.
Release Cadence We’ve moved to releasing Sonobuoy on a weekly basis as long as we have actual code changes. There had been a few instances in the past where features were on the main code branch and being used by developers but not readily available to the wider community and we want to limit that.</description></item><item><title>Skip the Boilerplate and Start Testing</title><link>https://sonobuoy.io/plugin-starter/</link><pubDate>Tue, 09 Nov 2021 00:00:00 +0000</pubDate><guid>https://sonobuoy.io/plugin-starter/</guid><description>TL;DR; Try out our new plugin skeleton which provides a useful starting point for developing integration tests for Kubernetes native workloads/components.
Introduction When you decide to test your Kubernetes native code it can be a big chore. Typically, you have to choose either:
Start a new project: Simple in concept but you&amp;rsquo;re left with a ton of boilerplate code so that you can do simple things like check if your app is running.</description></item><item><title>Plugin Management with Sonobuoy</title><link>https://sonobuoy.io/plugin-management/</link><pubDate>Wed, 13 Oct 2021 00:00:00 +0000</pubDate><guid>https://sonobuoy.io/plugin-management/</guid><description>Introduction Our new plugin management features are meant to solve 3 of the most common issues when routinely developing custom Sonobuoy plugins (and plugin configurations).
First, almost as a matter of law, if you are quickly iterating against a plugin you tend to accumulate more and more plugin definition files (*.yaml). As the number of plugin definitions increase (e.g. quicktest.yaml, version2.yaml, debug1.yaml, etc) it becomes cluttered and difficult to recall the different changes.</description></item><item><title>Understanding Kubernetes E2E Tests</title><link>https://sonobuoy.io/understanding-e2e-tests/</link><pubDate>Tue, 06 Jul 2021 00:00:00 +0000</pubDate><guid>https://sonobuoy.io/understanding-e2e-tests/</guid><description>One of the most common questions that we get from Sonobuoy users is: “Why are so many tests skipped?” Understandably, users want to know that they are running the right set of tests for their Kubernetes clusters but the complexity of the test suite, misnomers, and inaccurate language can make that difficult.
We wanted to explain the nomenclature of the Kubernetes test suite and describe when and how to run those tests.</description></item><item><title>Running E2E Tests On Windows Clusters</title><link>https://sonobuoy.io/windows-e2e-tests-with-sonobuoy/</link><pubDate>Mon, 21 Jun 2021 00:00:00 +0000</pubDate><guid>https://sonobuoy.io/windows-e2e-tests-with-sonobuoy/</guid><description>In the previous blog post, we introduced Sonobuoy support for Windows, showed how to set up a Kubernetes cluster which includes Windows nodes, and ran a custom Windows plugin.
In this post we would like to focus on the running the the Kubernetes end-to-end tests against your cluster. Instead of heavily modifying the e2e plugin itself in order to run on Windows, we&amp;rsquo;ve provided a new plugin (3 variants of a plugin really) which wrap all the necessary configuration together.</description></item><item><title>Introducing Support for Windows Clusters</title><link>https://sonobuoy.io/sonobuoy-adds-windows-support/</link><pubDate>Mon, 07 Jun 2021 00:00:00 +0000</pubDate><guid>https://sonobuoy.io/sonobuoy-adds-windows-support/</guid><description>Sonobuoy’s latest release, v0.51.0 introduces beta support for Windows, closing one of our longest standing roadmap items. This means that the Sonobuoy image can run on Windows nodes (including Windows versions &amp;ldquo;1809&amp;rdquo;, &amp;ldquo;1903&amp;rdquo;, &amp;ldquo;1909&amp;rdquo;, &amp;ldquo;2004&amp;rdquo;, and &amp;ldquo;20H2&amp;rdquo;) in Kubernetes clusters as well as having a Windows compatible Sonobuoy client. This will simplify testing of Kubernetes clusters with Windows nodes and speed development of full Kubernetes support and certification of Windows clusters.</description></item><item><title>A Better Experience with Airgap Testing</title><link>https://sonobuoy.io/better-airgap/</link><pubDate>Fri, 30 Apr 2021 00:00:00 +0000</pubDate><guid>https://sonobuoy.io/better-airgap/</guid><description>TL;DR; TODO
START Command to get images from nodes kubectl get nodes -o json | jq -r &amp;lsquo;.items|.[]|.status.images|.[]|.names[]&amp;rsquo; | sort | uniq
So I want to try and execute as few steps as possible and not have any images outside of my own registry All the images is a ton though! Especially windows images.
END Introduction When you decide to test your Kubernetes native code it can be a big chore.</description></item><item><title>Establishing Reliability-As-Code via Sonobuoy</title><link>https://sonobuoy.io/reliability-scanner-kubernetes-clusters/</link><pubDate>Thu, 18 Mar 2021 00:00:00 +0000</pubDate><guid>https://sonobuoy.io/reliability-scanner-kubernetes-clusters/</guid><description>We are happy to introduce the Reliability Scanner for Kubernetes as a Sonobuoy Plugin! It is a light-weight Go program that includes an extensible set of reliability assessments, or checks, performed against various components of a cluster, such as Pods, Namespaces, Services, etc. The Reliability Scanner runs as a container that serves as a Sonobuoy plugin and uses a configuration file to define customized checks. Kubernetes cluster operators can then configure appropriate constraints to run reliability scanner checks against their clusters.</description></item><item><title>Introducing Sonobuoy v0.50</title><link>https://sonobuoy.io/sonobuoy-v0-50/</link><pubDate>Thu, 18 Mar 2021 00:00:00 +0000</pubDate><guid>https://sonobuoy.io/sonobuoy-v0-50/</guid><description>In December, we announced that Sonobuoy releases will be decoupled from Kubernetes releases along with plenty of other items on the roadmap. With this release, Sonobuoy continues to make progress and this write up highlights two of its major themes.
New version number 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.</description></item><item><title>Decoupling Sonobuoy and Kubernetes</title><link>https://sonobuoy.io/decoupling-sonobuoy-and-kubernetes/</link><pubDate>Fri, 11 Dec 2020 00:00:00 +0000</pubDate><guid>https://sonobuoy.io/decoupling-sonobuoy-and-kubernetes/</guid><description>Historically, we have been following Kubernetes releases to ensure the usability of Sonobuoy with the most recent Kubernetes version. We are excited to announce that beginning Sonobuoy 0.20, Sonobuoy releases will no longer be attached to Kubernetes releases.
Under the hood Sonobuoy provides a one-stop solution to run Kubernetes conformance testing. It also handles airgapped testing nicely for users to prepare container images used by the test suite. This feature, however, is also the reason why Sonobuoy releases are tied to Kubernetes releases &amp;ndash; Sonobuoy maintains a copy of list of images internally for each Kubernetes minor.</description></item><item><title>The Road to Sonobuoy version 1.0</title><link>https://sonobuoy.io/the-road-to-v1/</link><pubDate>Fri, 11 Dec 2020 00:00:00 +0000</pubDate><guid>https://sonobuoy.io/the-road-to-v1/</guid><description>After numerous releases, the Sonobuoy project has planted itself as a permanent and useful fixture in the cloud native community. The release of version 0.20 marks the start of a vision to take the project toward a 1.0 release. There are many enhancements, however, that need to be put in place before the project can get to this coveted milestone. This blog is part roadmap and part vision statement to the community of where the team would like to take the project to get to 1.</description></item><item><title>Who has access to your Kubernetes cluster?</title><link>https://sonobuoy.io/who-can-plugin/</link><pubDate>Fri, 15 May 2020 00:00:00 +0000</pubDate><guid>https://sonobuoy.io/who-can-plugin/</guid><description>The Sonobuoy team is continuing to expand its range of custom plugins and we would like to introduce the latest plugin in our collection: who-can.
This plugin utilizes a project from Aqua Security: kubectl-who-can. kubectl-who-can shows which subjects have RBAC permissions to perform actions (verbs) against different resources in all namespaces in your Kubernetes clusters. It shows which subjects can perform those actions, but also the role bindings and cluster role bindings that enable them to do so.</description></item><item><title>Does Testing Kubernetes Conformance Leave You in the Dark? Get Progress Updates as Tests Run</title><link>https://sonobuoy.io/conformance-testing-with-progress-updates/</link><pubDate>Fri, 06 Dec 2019 00:00:00 +0000</pubDate><guid>https://sonobuoy.io/conformance-testing-with-progress-updates/</guid><description>Does Testing Kubernetes Conformance Leave You in the Dark? Get Progress Updates as Tests Run In Sonobuoy 0.15.4, we introduced the ability for plugins to report their plugin&amp;rsquo;s progress to Sonobuoy by using a customizable webhook. Reporting status is incredibly important for long-running, opaque plugins like the e2e plugin, which runs the Kubernetes conformance tests.
We&amp;rsquo;re happy to announce that as of Kubernetes 1.17.0, the Kubernetes end-to-end (E2E) test framework will utilize this webhook to provide feedback about how many tests will be run, have been run, and which tests have failed.</description></item><item><title>A Sonobuoy Plugin to Check Cluster Security with the CIS Kubernetes Benchmark</title><link>https://sonobuoy.io/cis-benchmark-plugin/</link><pubDate>Mon, 18 Nov 2019 00:00:00 +0000</pubDate><guid>https://sonobuoy.io/cis-benchmark-plugin/</guid><description>Sonobuoy was always designed to facilitate third-party plugins in order to accommodate custom testing requirements but, until recently, the design of Sonobuoy made some advanced plugins impossible to create.
One of the most requested plugins is for the CIS Kubernetes Benchmark from the Center for Internet Security (CIS). These benchmarks are prescriptive tests for establishing a secure configuration posture for Kubernetes. However, we had difficulty implementing them as a Sonobuoy plugin until recently due to their numerous customization requirements, which were not supported.</description></item><item><title>Simple Approaches to Customizing the Kubernetes E2E Tests</title><link>https://sonobuoy.io/custom-e2e-image/</link><pubDate>Wed, 09 Oct 2019 00:00:00 +0000</pubDate><guid>https://sonobuoy.io/custom-e2e-image/</guid><description>Simple Approaches to Customizing the Kubernetes E2E Tests Sonobuoy can be used to run any set of custom tests and data-gathering logic, but the most common use case continues to be running the Kubernetes E2E tests.
The E2E test image is maintained by the Kubernetes community and is automatically generated for each release of Kubernetes. The test image bundles:
The binary, which contains the test logic Ginkgo, a tool for running tests An entrypoint script, which starts the tests and reports the results to Sonobuoy Historically, the entrypoint for the image was a bash script, which started the tests.</description></item><item><title>Announcing a new GitHub home for Sonobuoy</title><link>https://sonobuoy.io/new-github-org/</link><pubDate>Tue, 01 Oct 2019 00:00:00 +0000</pubDate><guid>https://sonobuoy.io/new-github-org/</guid><description>Big news! We are now part of a brand new GitHub organization: VMware Tanzu. VMware Tanzu is a new family of projects, products and services for the cloud native world. The Sonobuoy project is a critical part to conformance tests on Kubernetes, so it makes sense that it would be moved to sit alongside all the other VMware-supported cloud native repositories. You can read more about this change in this VMware blog post.</description></item><item><title>Recent Improvements in Sonobuoy</title><link>https://sonobuoy.io/summary-of-improvements/</link><pubDate>Wed, 25 Sep 2019 00:00:00 +0000</pubDate><guid>https://sonobuoy.io/summary-of-improvements/</guid><description>With the recent release of Sonobuoy 0.16.0, we thought it would be a good time to recap all the improvements made to Sonobuoy in our recent releases.
First off, Sonobuoy now supports Kubernetes 1.16.0 clusters. Secondly, in the past three months we’ve had seven releases and made major improvements in almost every area of Sonobuoy. There are too many changes to list them all, so check out our release notes for more information.</description></item><item><title>Customizing Plug-in PodSpecs</title><link>https://sonobuoy.io/customizing-plugin-podspecs/</link><pubDate>Mon, 16 Sep 2019 00:00:00 +0000</pubDate><guid>https://sonobuoy.io/customizing-plugin-podspecs/</guid><description>The Sonobuoy team is continuing to work on one of our main goals: improving the experience for users who want to create their own custom plug-ins.
With the release of Sonobuoy 0.15.2, we’ve introduced a new option in the plug-in definition, podSpec. This option allows you to customize the Kubernetes PodSpec used by Sonobuoy when you create Pods or DaemonSets, giving you even more flexibility and control over how your plug-ins run on your Kubernetes cluster.</description></item><item><title>Simplified Results Reporting with Sonobuoy 0.15.1</title><link>https://sonobuoy.io/simplified-results-reporting-with-sonobuoy/</link><pubDate>Wed, 07 Aug 2019 00:00:00 +0000</pubDate><guid>https://sonobuoy.io/simplified-results-reporting-with-sonobuoy/</guid><description>Sonobuoy 0.15.1 introduces an entirely new feature that promises to make it easier than ever to see the results of your plug-ins.
The new CLI command, sonobuoy results, targets a results tarball and can report on which tests pass, fail, or get skipped. Unlike the sonobuoy e2e command, this new command has been generalized to work with different types of plug-ins and can be extended to work with different formats.</description></item><item><title>Setting Environment Variables for Plugins on the Fly with Sonobuoy 0.15.0</title><link>https://sonobuoy.io/env-vars-on-the-fly/</link><pubDate>Wed, 26 Jun 2019 00:00:00 +0000</pubDate><guid>https://sonobuoy.io/env-vars-on-the-fly/</guid><description>With the release of Sonobuoy 0.15.0, we continue to support one of our top roadmap goals: enhanced support for custom plugins. It is now possible to easily modify the environment variables of any plugin without editing a YAML file.
Sonobuoy, an open source diagnostic tool, runs upstream Kubernetes tests to generate reports that help you understand the state of your cluster. Sonobuoy is the underlying technology powering the Certified Kubernetes Conformance Program, which was created by the Cloud Native Computing Foundation (CNCF) and is used by every Certified Kubernetes Service Provider.</description></item><item><title>Certifying Kubernetes with Sonobuoy</title><link>https://sonobuoy.io/certifying-kubernetes-with-sonobuoy/</link><pubDate>Wed, 15 May 2019 00:00:00 +0000</pubDate><guid>https://sonobuoy.io/certifying-kubernetes-with-sonobuoy/</guid><description>There are many ways to create Kubernetes clusters and many environments that can host them. As a result, platform operators find it difficult to determine whether a cluster is properly configured and whether it is working as it should.
Sonobuoy is an open-source diagnostic tool that makes it easier to understand the state of a Kubernetes cluster by running a set of upstream Kubernetes tests in an accessible and non-destructive manner.</description></item><item><title>Sonobuoy 101</title><link>https://sonobuoy.io/sonobuoy-101/</link><pubDate>Mon, 13 May 2019 00:00:00 +0000</pubDate><guid>https://sonobuoy.io/sonobuoy-101/</guid><description>Given that there are many ways to create Kubernetes clusters and many environments used to host them, those tasked with maintaining a cluster are often left wondering whether it is ‘correct’. Is it properly configured? Does it work as it should?
Sonobuoy is a diagnostic tool that aims to address these questions. Sonobuoy makes it easier to understand the state of a Kubernetes cluster by running a set of Kubernetes conformance tests in an accessible and non-destructive manner.</description></item><item><title>Fast and Easy Sonobuoy Plugins for Custom Testing of Almost Anything</title><link>https://sonobuoy.io/custom-testing/</link><pubDate>Tue, 30 Apr 2019 00:00:00 +0000</pubDate><guid>https://sonobuoy.io/custom-testing/</guid><description>Previously posted on the VMware Cloud Native Apps blog
Today we are releasing Sonobuoy 0.14.2, which delivers on one of our top roadmap goals: increased support for custom plugins, allowing developers and operators to extend Sonobuoy with additional tests and data gathering. It is now possible to easily create a plugin from a Docker image and run it within Sonobuoy without manually editing any YAML files.
Sonobuoy, an open source diagnostic tool, runs upstream Kubernetes tests to generate reports that help you understand the state of your cluster.</description></item><item><title>Isolated to Conformant - Testing Air-Gapped Kubernetes with Sonobuoy 0.14</title><link>https://sonobuoy.io/isolated-to-conformant/</link><pubDate>Tue, 02 Apr 2019 00:00:00 +0000</pubDate><guid>https://sonobuoy.io/isolated-to-conformant/</guid><description>Previously posted on the VMware Cloud Native Apps blog
Today we are releasing Sonobuoy 0.14.0, which delivers on one of our top roadmap goals: support for running Kubernetes end-to-end tests in air-gapped environments. It is now possible to run the end-to-end suite and validate your cluster’s state without Internet connectivity or investment in a custom, ad hoc work around.
Air-Gapped Installations and Testing Running critical systems in air-gapped environments, where the system can’t reach out to the Internet, has long been a common practice to limit the attack surface.</description></item></channel></rss>