Ephemeral environments are becoming the standard for fast moving software teams. Platforms like Okteto, Qovery, Shipyard, Garden.io, and vCluster make it easy to spin up temporary Kubernetes clusters or namespaces for each pull request, branch, or feature.
Testkube ensures these environments are fully testable just like dev, staging, or production. You can run complete test suites in short-lived clusters, trigger executions via your pipeline or CLI, and collect results without any custom setup.
And because Testkube uses a centralized control plane, you get test consistency across every ephemeral, long-lived, or remote environment.


One of the biggest challenges with ephemeral testing is losing access to logs, artifacts, and result history once the environment is gone.
Testkube solves this by storing all test results centrally, even after the underlying namespace or cluster is deleted.
Wherever you build, Testkube makes Kubernetes-native testing a natural part of your workflow.
Whether you're provisioning entire clusters or just temporary namespaces, Testkube adapts to how your team builds and tests software. Every test run connects back to a central control plane, ensuring results are always visible, comparable, and easy to trace.
Ephemeral testing becomes a core part of your release pipeline—not a workaround.


Testkube supports a multi-agent model, ideal for fully isolated testing in dynamic clusters. When your CI/CD pipeline provisions a short-lived environment, it can:
Each test result is linked to its origin environment, offering full traceability—even after the cluster is gone.
Testkube is designed for automation. You can spin up ephemeral environments with platforms like Okteto, Qovery, Garden, or Shipyard, then trigger test workflows through:
Testkube also supports floating licenses and unlimited runner agents, so you can run tests in parallel across multiple environments without bottlenecks.e.


