Skip to main content
New to Testkube? Unleash the power of cloud native testing in Kubernetes with Testkube. Get Started >

Testkube Custom Resources

Most Testkube objects like Workflows, WorkflowTemplates, Triggers, etc. are defined as Custom Resources and stored in the cluster where your Agents are installed.

The following Resource Group/Versions are available (click for documentation)

tip

More detailed schema docs are also available at https://doc.crds.dev/github.com/kubeshop/testkube-operator

The current definitions can be found in the kubeshop/testkube-operator repository.

Checking installed CRDs

You can always check the list of all CRDs using kubectl configured to point to your Kubernetes cluster with Testkube installed:

kubectl get crds -n testkube
Expected output:
NAME                                               CREATED AT
executors.executor.testkube.io 2024-05-31T09:53:09Z
scripts.tests.testkube.io 2024-05-31T09:53:09Z
templates.tests.testkube.io 2024-05-31T09:53:09Z
testexecutions.tests.testkube.io 2024-05-31T09:53:09Z
tests.tests.testkube.io 2024-05-31T09:53:09Z
testsources.tests.testkube.io 2024-05-31T09:53:09Z
testsuiteexecutions.tests.testkube.io 2024-05-31T09:53:09Z
testsuites.tests.testkube.io 2024-05-31T09:53:09Z
testtriggers.tests.testkube.io 2024-05-31T09:53:09Z
testworkflowexecutions.testworkflows.testkube.io 2024-05-31T09:53:09Z
testworkflows.testworkflows.testkube.io 2024-05-31T09:53:09Z
testworkflowtemplates.testworkflows.testkube.io 2024-05-31T09:53:09Z
webhooks.executor.testkube.io 2024-05-31T09:53:09Z

To check details on one of the CRDs, use describe:

kubectl describe crd testworkflows.testworkflows.testkube.io
Expected output:
Name:         testworkflows.testworkflows.testkube.io
Namespace:
Labels: app.kubernetes.io/managed-by=Helm
Annotations: controller-gen.kubebuilder.io/version: v0.15.0
meta.helm.sh/release-name: testkube
meta.helm.sh/release-namespace: testkube
API Version: apiextensions.k8s.io/v1
Kind: CustomResourceDefinition
...