A tool for running local Kubernetes clusters using Docker container nodes, designed for testing and development.
kind (Kubernetes IN Docker) is a tool for running local Kubernetes clusters using Docker container nodes. It solves the problem of needing a lightweight, portable Kubernetes environment for testing, development, and CI workflows without the complexity of full-scale deployments.
Kubernetes developers, testers, and CI/CD engineers who need to test Kubernetes features, run integration tests, or develop applications locally in a Kubernetes environment.
Developers choose kind for its simplicity, cross-platform support, and ability to create multi-node clusters quickly using Docker. Its CNCF certification ensures compatibility with Kubernetes standards, making it a reliable choice for testing and development.
Kubernetes IN Docker - local clusters for testing Kubernetes
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Supports multi-node and high-availability clusters, enabling realistic testing scenarios for Kubernetes features and development workflows beyond single-node setups.
Runs on Linux, macOS, and Windows, as highlighted in the README, making it accessible for developers across different operating systems without VM overhead.
Ensures compatibility with Kubernetes standards, providing a reliable and conformant base for testing and development, which is crucial for CI/CD pipelines.
Allows building Kubernetes directly from source code, ideal for testing custom changes or unreleased features, as detailed in the installation guide.
The project is still a work in progress with a 1.0 roadmap, meaning potential breaking changes, incomplete features, and less stability for production-like use.
Requires Docker or a compatible runtime like podman, limiting adoption in environments where container runtimes are restricted or unavailable, as noted in the prerequisites.
Multi-node and custom setups require configuration files, which can be less intuitive for quick, ad-hoc usage compared to simpler tools with more guided interfaces.