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

Deployment Architectures

Testkube contains two sub-systems:

  • A Control Plane which includes the Dashboard, Storage for Results/Artifacts, Cluster Federation, etc
  • An Agent running in your cluster that manages Testkube resources, runs tests, gathers results, etc.

The two sub-systems can be deployed in variety of ways to give flexibility into where your tests are executed and where test logs and artifacts are stored.

A more detailed overview is available in the Architecture Reference document.

Testkube On-Prem

Testkube On-Prem is the default architecture and has both the control plane and a single agent within the same namespace. You will have one single environment.

To deploy this you will want to look at either installing with CLI or installing with Helm, respectively for an out-of-the-box experience or more configurability.

Deployment with single agent

Testkube Cloud

Testkube Cloud has a control plane that is managed by the Testkube team. You only have to run a stateless agent which makes operations a breeze. To get started simply visit https://app.testkube.io.

info

Your proprietory code never touches our servers, only test logs and artifacts will be stored.

Deployment with managed control plane

Testkube On-Prem Multicluster

A Testkube On-Prem variant which has the control plane in one namespace with multiple agents in other namespaces or clusters. You will create an environment for each of your clusters.

To deploy this you will first want to deploy a control plane without an agent and afterwards deploy an agent that joins Testkube.

Deployment with federated agents

Testkube Standalone Agent

Testkube standalone agent works without a control plane. The standalone agent includes the full test orchestration engine: you can apply Tests, TestWorkflows, etc and execute them with your CLI. Overal there are few reasons to run the agent without the control plane.

To learn more you can visit deploying the standalone agent.

Deployment with standalone agent