Kubetest2
github.com
- Free plan
- Open source
- API
- Self-hosted
What Kubetest2 is
Kubetest2 is a free, open-source framework for deploying Kubernetes clusters and running end-to-end tests against them. Separate executables handle deployers, cluster lifecycle management, and test runners, reducing coupling between those parts and supporting implementations outside the project. Reference deployers include GCE, GKE, kind, and noop, with noop able to use an existing cluster. Reference testers include clusterloader2, exec, Ginkgo, and node end-to-end runners. The README also lists external deployers for AKS, kOps, Terraform, and EC2, plus an external kOps tester. Kubetest2 runs locally and supports Terraform, provisioning tests, deployed checks, and deployments involving Google Cloud, AWS, and Azure. Go installation commands are provided for the framework and reference components. The project is currently unversioned and unreleased, and makes a best-effort attempt to work with in-development and supported Kubernetes releases.
Who it suits
Kubetest2 suits Kubernetes developers and operators who need local cluster deployment and end-to-end testing. It fits users working with listed cloud deployers, Terraform, or existing clusters.
Good to know, and what to watch
- Deploys clusters and runs end-to-end tests
- Separate deployer and tester executables
- Reference deployers include GCE, GKE, and kind
- Reference testers include Ginkgo and clusterloader2
- Apache License 2.0
- Currently unversioned and unreleased
- Best-effort support for Kubernetes releases
- Requires local Go installation commands
Plans
Every plan and priceApache License 2.0
Open source
The verdict
Kubetest2 combines Kubernetes provisioning and end-to-end testing through replaceable deployers and testers. Its broad reference and external implementations are useful, but the project’s unreleased status calls for careful compatibility planning.
What the maker publishes
- Architecture
- The framework uses separate executables to invoke deployers, manage cluster lifecycles, and run tests. source
- Architecture
- The system consists of a discovery and orchestration binary, deployer binaries that manage cluster lifecycles, and tester binaries that execute tests. source
- Artifact handling
- The ARTIFACTS environment variable identifies where logs and other test outputs should be stored. source
- Cloud and local workflows
- The e2e-framework documentation demonstrates both noop execution against an existing cluster and KinD cluster creation and teardown. source
- Command syntax
- The documented command form places deployer flags before a double dash and tester arguments after it. source
- Community ownership
- The CNCF conformance working group says SIG Testing handles the mechanics of Kubernetes conformance tests while SIG Architecture owns the conformance definition. source
- Community support
- The README directs users to Kubernetes community Slack and a mailing list to contact maintainers. source
- Compatibility policy
- Maintainers aim to keep the tool and reference implementations working with the in-development Kubernetes version and currently supported releases. source
- Custom testers
- Custom testers must follow the naming convention, accept configuration arguments, use supplied environment variables, and return meaningful exit codes. source
- Deployers
- Reference deployers include GCE, GKE, kind, and noop, which can use an existing cluster. source
- Design goal
- Its separation of deployers and testers is intended to reduce coupling, keep the core small, and enable out-of-tree implementations. source
- Documentation depth
- pkg.go.dev exposes documented packages for application logic, deployers, testers, artifacts, build helpers, metadata, process execution, and shared types. source
- E2E framework controls
- That tester supports package selection, feature and assessment filters, dry runs, parallel execution, fail-fast behavior, kubeconfig selection, and Go test flags. source
- E2E framework integration
- The Kubernetes e2e-framework publishes a kubetest2 tester that can be installed with Go and placed on PATH. source
- Extensibility
- Its design aims to minimize coupling between deployers and testers and encourage out-of-tree implementations. source
- External implementations
- The README lists external deployers for AKS, kOps, Terraform, and EC2, plus a kOps tester. source
- External integrations
- The project lists external implementations for AKS, kOps, Terraform, EC2, and a kOps tester. source
- Go API
- The public Go types package defines deployer interfaces for build, up, down, status, log dumping, kubeconfig, initialization, finalization, post-test handling, provider identification, and version reporting. source
- Independent architecture description
- A Kubernetes Day India presentation describes Kubetest2 as orchestrating cluster creation, Kubernetes builds, test execution, log collection, and cluster deletion. source
- Independent kOps guidance
- The kOps documentation recommends Kubetest2 as the preferred framework for Kubernetes end-to-end testing and says it downloads artifacts into ./_artifacts. source
- Independent training coverage
- Class Central lists a free, 40-minute Linux Foundation video covering cloud testing, architecture, log collection, disposal, and custom deployer development. source
- Install
- The README provides Go install commands for Kubetest2, reference deployers, and testers. source
- Installation
- The project documents installing the core, reference deployers, and testers with Go's go install command. source
- Known compatibility gap
- The Kubernetes CI migration proposal says some tests need client-server version-skew checking that Kubetest2 did not yet support. source
Checked against the maker's pages on 14 Oct 2026.