Multicluster

Testkube can federate multiple clusters. Conceptually, each cluster maps to an environment within Testkube. You will require a pro plan to deploy multiple Testkube agents.

info

The commands below that connect to on-prem will likely need to add an --agent-uri flag or they will instead by default connect to Testkube Cloud.

Deploy an agent that will join Testkube

You can add another agent to an existing Testkube deployment within a couple of minutes. Get started by going to the Dashboard and create a new environment. Afterwards it will show you a command that can be used to bootstrap the agent in another cluster. The command looks as follows:

Multiple agents within the same cluster

It's possible to install multiple agents within the same cluster. This requires modified values for the second agent to prevent creating cluster-wide objects twice which is disallowed by Kubernetes. Make the following changes to the values of the second agent:

testkube-operator:
  enabled: false

Deploy a control plane without an agent

By default, Testkube will create an environment within the same namespace as the control plane. You can choose for a minimal deployment without a control plane. Once started, you can deploy agents that will join your control plane as described above.

Within the Helm values.yaml make the following changes:

testkube-agent:
-  enabled: true
+  enabled: false

testkube-cloud-api:
  api:
    features:
-      bootstrapEnv: "my-first-environment"
-      bootstrapAgentTokenSecretRef: "testkube-default-agent-token"