Skip to main content


Frequently asked questions regarding your Testkube installation.

How do I install Testkube?

To install Testkube, you'll need to install Testkube CLI (which is currently available on MacOS, Linux, and Windows) and install Testkube's API in your cluster using Helm.

You can read more about how to install and get Testkube up and running by following the instructions in our Installation Guide.

Can I run any test in Testkube?

Yes, if we're not currently supporting a testing framework you need, you can create your custom executor and configure it to run any type of tests that you want. These custom test types can be added to your Testkube installation and/or contributed to our repo.

You can read more about creating Custom Executors here.

How do I expose Testkube to the internet?

To expose Testkube to the Internet, you will need to create ingresses both for Testkube's API and Testkube's dashboard.

You can follow the example ingresses created for our Testkube Demo here and here.

How do I setup my CI/CD to trigger tests?

There's different ways to integrate Testkube with your CI/CD pipeline. You can directly use the command-line interface, or if you use GitHub, you can create GitHub actions.

Read more about the process here.

If you're working with ArgoCD, this blogpost will be useful.

Does Testkube have customer support?

To contact our team for support, we have a few channels available. You can reach us via our Discord server by simply posting your issues on #testkube-general or #testkube-bugs.

You can also create an issue on GitHub.

Why is the UI not working or does not return results?

  • Make sure the API endpoint is configured:


  • Make sure the endpoint is providing data, e.g. accessing the executors path:
curl <endpoint>/v1/executors 
  • If no data is provided, make sure that all the Testkube components are running properly:
kubectl get pods -n testkube
pod/testkube-api-server-8445fd7b9f-jq5rh 1/1 Running 0 10d
pod/testkube-dashboard-99f4c6cf5-x4dkz 1/1 Running 0 12d
pod/testkube-minio-testkube-76786f8f64-9nl4c 1/1 Running 1 24d
pod/testkube-mongodb-74587998bb-8pzl2 1/1 Running 0 12d
pod/testkube-operator-controller-manager-77ffbb8fdc-rxhvx 2/2 Running 0 5d23h

Opening the Dashboard Using CLI Is Not Working

If there is a timeout error reported:

testkube dashboard
checking readiness of services (error: timed-out waiting for dashboard and api)

Make sure that there is not another dashboard process running in the background like in the example below:

ps aux | grep dashboard
user 76005 0.0 0.0 408628368 1648 s002 S+ 12:32PM 0:00.00 grep dashboard
user 75985 0.0 0.1 409292320 43584 s001 S+ 12:32PM 0:00.12 kubectl port-forward --namespace testkube deployment/testkube-dashboard 8080:8080
user 75984 0.0 0.1 409263376 37488 s001 S+ 12:32PM 0:00.22 testkube dashboard

Also, there might be some other process listening on the same port. To debug this, try port-forwarding manually:

kubectl port-forward svc/testkube-dashboard 8080
kubectl port-forward svc/testkube-api-server 8088

Check for errors and try accessing: http://localhost:8081/apiEndpoint?apiEndpoint=localhost:8088/v1

If you see errors like:

Unable to listen on port 8080: Listeners failed to create with the following errors: [unable to create listener: Error listen tcp4 bind: address already in use unable to create listener: Error listen tcp6 [::1]:8080: bind: address already in use]
error: unable to listen on any of the requested ports: [{8080 8080}]

Please stop the application that listens on 8080, 8088 ports.

Access the Service Under Test(SUT) Using Testkube

  • Services inside the same Kubernetes cluster can be accessed using the address \<service-name>.\<service-namespace>.svc.cluster.local:\<port-number>. If there are network restrictions configured, Testkube will need permissions to access the SUT over the local network of the cluster.
  • If Testkube and the SUT are not in the same cluster, SUT will have to be exposed to Testkube using an Ingress or a Load Balancer.

If this does not solve the issue that you encountered or you have other questions or comments, please contact us on Discord.