testkube VS goss

Testkube is an open-source project, part of the CNCF landscape, and testing framework designed for testers and developers who use Kubernetes. It integrates test orchestration and execution into Kubernetes and your CI/CD/GitOps pipeline. You can automate the execution of your tests, regardless of the testing framework, by using Testkube's executors or creating your own.

For tips from other DevOps and GitOps enthusiasts, check out our active Discord or find our entire open source project on GitHub! We’re also on Twitter (@testkube_io), where we’re always sharing the latest news in our journey to become the most complete and beloved Kubernetes-native testing framework.

With Testkube, you would do it by:

Download the latest release on GitHub

If you’re interested in the code of our test, feel free to check it here (just import file as Postman collection) it’s just exported Postman collections JSON file that tests against our Testkube API defined in OpenAPI spec

TestKube documentation

What runs the tests is something called executors, currently the project already has Cypress, Postman & k6 executors and it's very easy to write new ones. You can open a github issue asking for a new executor that you would like to have (or you can also contribute it yourself if you are into that 😋)

Currently in all projects on which I'm working on using REST-based API defined by OpenAPI spec v3. It feels natural and widely adopted in all communities. The project is open-source (kubeshop/testkube) and the main goal is to simplify testing in the Kubernetes world - where RESTful APIs (probably) is the first technology that comes to your mind when starting such a project.

Certain checks may be possible with goss and the kgoss wrapper: https://github.com/goss-org/goss/tree/master/extras/kgoss

Docker would work. I suggest also integrating infrastructure tests to validate your install script behaved as expected. For example, you could use goss.

I've used https://github.com/goss-org/goss in the past and enjoyed it

To answer my own question... https://github.com/goss-org/goss looks like it might do the job - at least for Linux. Windows support is alpha - and there isn't a wealth of CIS benchmarks. Might be a good project to contribute to

Adding an extra layer of security on the container image to verify if it is working as expected and has all required files with correct permissions. We can use dgoss to do validation tests of container images.

Bit of a strange one here - Goss. This is a testing tool that we use on all of our servers to validate they are working as expected. Think of it as a sanity check after changes. We have a set of tests setup that validate that the server is working as expected and we run it automatically after any change.

check out https://github.com/aelsabbahy/goss

Use GOSS, a YML-based open-source tool that can assert the test results (i.e., verifying if the SSH port 22 is closed or not).