thatchd

README

Thatchd

Thatchd is a testing framework for Kubernetes where test cases are first class Kubernetes resources that are dispatched and executed by a controller based on the cluster state. It allows developers to leverage the Kubernetes controller pattern and Custom Resources by injecting their custom testing logic.

Overview

Thatchd is made of the following components, backed by Custom Resources

TestSuite

The test suite is the central component of the test process. It reconciles a status object, that aggregates all the relevant information of the testing process. This object may be of any type, allowing the developer to use whatever information is necessary for the testing domain.

TestWorker

The test worker supports the testing process by progressing tasks that may result in other test cases being dispatches. Test workers are dispatched based on a condition on the test suite state. When dispatched, the result of their execution results in a mutation of the testing state.

TestCase

Like test workers, test cases are dispatched based on a condition on the test suite state, and are responsible of performing the testing logic. If the test fails, it's reflected in the TestCase CR

Try it

Thatchd is still under early development, but you can try it's functionallity with the example test suite that's included in the repo.

Pre-requisites

• operator-sdk v1.0.0
• Admin access to a Kubernetes cluster

Set up

Clone the repo and install resources in the cluster

git clone https://github.com/sergioifg94/thatchd.git
cd thatchd
make install

Start running the operator

make run ENABLE_WEBHOOKS=false

Create CRs

The example test suite is included in the repo. The logic is injected to the TestSuite and TestCase controllers, and defined in the example package

This example suite tests that Pods in the namespace have specific annotations, failing the test case if they don't.

TestSuite

See the source code of the example TestSuite reconciler:

👓 example/testsuite.go

Create the TestSuite CR with the PodsSuiteProvider

apiVersion: testing.thatchd.io/v1alpha1
kind: TestSuite
metadata:
  name: test-pods
spec:
  initialState: '{}'
  stateStrategy:
    provider: PodsSuite

Once created, Thatchd will reconcile the status with a list of Pods in the namespace. Go ahead and create a simple Pod. Thatchd will reconcile the status field accordingly

status:
  currentState: |-
    {
      "my-pod": true
    }

ℹ You can use any Go type as test state, leveraging the language type information

TestCase

See the source code of the example TestCase implementation:

👓 example/testcase.go

The example test case will be dispatched when a specific pod is annotated according to the TestSuite state. Create a TestCase CR to verify that the foo: bar annotation is set on the test-success Pod

apiVersion: testing.thatchd.io/v1alpha1
kind: TestCase
metadata:
  name: testcase-success
spec:
  strategy:
    configuration:
      expectedAnnotation: foo
      expectedValue: bar
      podName: test-success
    provider: PodAnnotation

ℹ️ The configuration field in the CR allows to reuse logic in multiple test cases

The test case won't be dispatched yet as the Pod hasn't been created

TestWorker

See the source code of the example TestWorker implementation:

👓 example/testworker.go

The example test worker will be dispatched when a specific pod is ready, and will annotate the pod with the configured annotation. Create a TestWorker CR to annotate the test-success Pod with foo: bar

apiVersion: testing.thatchd.io/v1alpha1
kind: TestWorker
metadata:
  name: testworker-success
spec:
  strategy:
    configuration:
      annotation: foo
      value: bar
      podName: test-success
    provider: PodAnnotationWorker

Test subject: test-success Pod

Create the Pod called test-success

apiVersion: v1
kind: Pod
metadata:
  name: test-success
  labels:
    app: hello-openshift
spec:
  containers:
    - name: hello-openshift
      image: openshift/hello-openshift
      ports:
        - containerPort: 8080

Once the Pod is ready, the TestWoker will be dispatched, and quickly executed, annotating the Pod and setting the suite status. When the Pod status is set to annotated, the TestCase will be dispatched and executed, verifying the annotation and setting the status to Finished