Testkube Custom Resources
In Testkube, Tests, Test Suites, Executors and Webhooks, Test Sources and Test Triggers are defined using Custom Resources. The current definitions can be found in the kubeshop/testkube-operator repository.
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 2023-06-15T14:49:11Z
scripts.tests.testkube.io 2023-06-15T14:49:11Z
templates.tests.testkube.io 2023-06-15T14:49:11Z
testexecutions.tests.testkube.io 2023-06-15T14:49:11Z
tests.tests.testkube.io 2023-06-15T14:49:11Z
testsources.tests.testkube.io 2023-06-15T14:49:11Z
testsuiteexecutions.tests.testkube.io 2023-06-15T14:49:11Z
testsuites.tests.testkube.io 2023-06-15T14:49:11Z
testtriggers.tests.testkube.io 2023-06-15T14:49:11Z
webhooks.executor.testkube.io 2023-06-15T14:49:11Z
To check details on one of the CRDs, use describe
:
kubectl describe crd tests.tests.testkube.io
Expected output:
Name: tests.tests.testkube.io
Namespace:
Labels: app.kubernetes.io/managed-by=Helm
Annotations: controller-gen.kubebuilder.io/version: v0.4.1
meta.helm.sh/release-name: testkube
meta.helm.sh/release-namespace: testkube
API Version: apiextensions.k8s.io/v1
Kind: CustomResourceDefinition
...
You can find the description of each CRD in the CRDs Reference section of the documentation.