- Home
- Infrastructure Testing Tools
- Kubetest2
On the recordRead 14 Oct 202644 facts
Kubetest2
Plans and prices
Apache License 2.0
Free
No charge under the license
Read 8 Oct 2026 · github.com
On the record
- Architecture
- The system consists of a discovery and orchestration binary, deployer binaries that manage cluster lifecycles, and tester binaries that execute tests.github.com · read 14 Oct 2026
- Artifact handling
- The ARTIFACTS environment variable identifies where logs and other test outputs should be stored.deepwiki.com · read 14 Oct 2026
- Cloud and local workflows
- The e2e-framework documentation demonstrates both noop execution against an existing cluster and KinD cluster creation and teardown.pkg.go.dev · read 14 Oct 2026
- Command syntax
- The documented command form places deployer flags before a double dash and tester arguments after it.github.com · read 14 Oct 2026
- Community ownership
- The CNCF conformance working group says SIG Testing handles the mechanics of Kubernetes conformance tests while SIG Architecture owns the conformance definition.github.com · read 14 Oct 2026
- Community support
- The README directs users to Kubernetes community Slack and a mailing list to contact maintainers.github.com · read 8 Oct 2026
- Compatibility policy
- Maintainers aim to keep the tool and reference implementations working with the in-development Kubernetes version and currently supported releases.github.com · read 14 Oct 2026
- Custom testers
- Custom testers must follow the naming convention, accept configuration arguments, use supplied environment variables, and return meaningful exit codes.deepwiki.com · read 14 Oct 2026
- Deployers
- Reference deployers include GCE, GKE, kind, and noop, which can use an existing cluster.github.com · read 8 Oct 2026
- Design goal
- Its separation of deployers and testers is intended to reduce coupling, keep the core small, and enable out-of-tree implementations.github.com · read 14 Oct 2026
- Documentation depth
- pkg.go.dev exposes documented packages for application logic, deployers, testers, artifacts, build helpers, metadata, process execution, and shared types.pkg.go.dev · read 14 Oct 2026
- 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.pkg.go.dev · read 14 Oct 2026
- E2E framework integration
- The Kubernetes e2e-framework publishes a kubetest2 tester that can be installed with Go and placed on PATH.pkg.go.dev · read 14 Oct 2026
- Extensibility
- Its design aims to minimize coupling between deployers and testers and encourage out-of-tree implementations.github.com · read 8 Oct 2026
- External implementations
- The README lists external deployers for AKS, kOps, Terraform, and EC2, plus a kOps tester.github.com · read 8 Oct 2026
- External integrations
- The project lists external implementations for AKS, kOps, Terraform, EC2, and a kOps tester.github.com · read 14 Oct 2026
- 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.pkg.go.dev · read 14 Oct 2026
- Independent architecture description
- A Kubernetes Day India presentation describes Kubetest2 as orchestrating cluster creation, Kubernetes builds, test execution, log collection, and cluster deletion.static.sched.com · read 14 Oct 2026