kind vs MicroShift
kind
kind.sigs.k8s.ioMicroShift
microshift.ioSide by side
| Figure | kind | MicroShift |
|---|---|---|
| Price from | Free | Free |
| Free plan | Yes | Yes |
| Free trial | — | — |
| Open source | — | — |
| Windows | Yes | — |
| macOS | Yes | Yes |
| Linux | Yes | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 1 | 1 |
| Spec score · Local Kubernetes Tools | 8.7 (#1) | 7.9 (#14) |
| License | The kind GitHub repository identifies its license as Apache-2.0. | The repository lists an Apache-2.0 license. |
| Networking | The documentation covers configuring ingress and Gateway API with cloud-provider-kind, which natively supports both. | Its design goals include tolerating severe networking constraints. |
| Purpose | kind runs local Kubernetes clusters using Docker container nodes and is designed primarily for Kubernetes testing, with local development and CI as other uses. | MicroShift optimizes OpenShift Kubernetes for small form factor and edge computing. |
Plans
In their own words
kind
kind runs local Kubernetes clusters with Docker container nodes, mainly for Kubernetes testing; local development and CI are also listed uses. It bootstraps cluster nodes with kubeadm and supports multi-node setups, including high availability. A configuration file can define worker and control-plane nodes, port mappings, and Kubernetes versions.
The tool can build Kubernetes release builds from source or use pre-published builds. It can detect Docker, Podman, or nerdctl as its container provider, including rootless providers subject to host and provider requirements. Users can load Docker images or an image archive into a cluster. Documentation covers ingress and Gateway API configuration with cloud-provider-kind, private registry workflows, and Kubernetes API audit logging.
MicroShift
MicroShift is a small-footprint OpenShift Kubernetes platform designed for edge computing. It aims to conserve CPU, memory, network, and storage resources and tolerate severe networking constraints. It runs as a single systemd service with a minimal OpenShift control plane and worker node. Included infrastructure services are DNS, an ingress router, service CA, OVN-Kubernetes CNI, and LVMS storage; optional components such as OLM, Gateway API, cert-manager, and SR-IOV come as separate RPM packages. The upstream build is for development and testing and runs without Red Hat subscriptions or pull secrets. Its listed operating-system options include CentOS 9 and 10, Fedora, Ubuntu, and macOS, with macOS using Podman machine in rootful mode. Minimum requirements include x86_64 or aarch64, Red Hat Enterprise Linux with Extended Update Support, 2 CPU cores, 2GB RAM, and 2GB free root storage. Production deployment can use bare metal or hypervisors supported and certified for Red Hat Enterprise Linux 9. The upstream build is free; pricing for other use is on request.