KubeFleet vs Mirantis Kubernetes Engine
KubeFleet
kubefleet.devMirantis Kubernetes Engine
docs.mirantis.comSide by side
| Figure | KubeFleet | Mirantis Kubernetes Engine |
|---|---|---|
| Price from | — | — |
| Free plan | — | — |
| Free trial | — | Yes |
| Open source | — | — |
| Web | — | Yes |
| Windows | — | Yes |
| Linux | — | Yes |
| API | Yes | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 0 | 1 |
| Spec score · Container Management Software | 7.2 (#21) | 8.1 (#10) |
| Architecture | KubeFleet uses hub and member agents, with member agents pulling resource manifests from the hub. | An MKE 4 cluster includes k0s, a container network interface, the MKE control plane, system services, and user services. |
| Management | It provides a multi-cluster control plane for deploying and managing resources across member clusters. | The mkectl command-line tool manages the cluster lifecycle using a declarative mke4.yaml configuration file. |
| Purpose | KubeFleet manages Kubernetes resources across multiple clusters using placement policies and scheduling. | MKE 4 is an enterprise Kubernetes platform built on the open-source k0s distribution. |
| Security | The documentation says KubeFleet reserves a namespace on the hub to isolate permissions and resources across member clusters. | Mirantis describes MKE 4 as secure by default and says its default components are FIPS-validated. |
| Support | The site directs users to GitHub discussions and issues for questions, feedback, and bug reports. | Mirantis offers a choice of 24/7 proactive support or managed services for MKE 4. |
Plans
In their own words
Mirantis Kubernetes Engine
Mirantis Kubernetes Engine (MKE 4) is a self-hosted enterprise Kubernetes platform built on the open-source k0s distribution. It supports deployment across public and private clouds, multi-cloud and hybrid-cloud environments, and bare-metal infrastructure. Teams manage cluster lifecycle with the mkectl command-line tool and a declarative mke4.yaml configuration file; standardized APIs and GitOps-based lifecycle management are also listed. A cluster combines k0s, a container network interface, the MKE control plane, system services, and user services. Calico is installed by default, with other network interface options supported. The web dashboard manages Kubernetes resources in an MKE-managed cluster. Backup and restore are supported, and the CLI upgrade process includes automated backups. Authentication through Dex supports OIDC, SAML, and LDAP, but not MFA. MKE 4 requires x86_64 and Linux manager/control-plane nodes; supported operating systems include specified Ubuntu, RHEL, and Rocky Linux versions, plus Windows Server worker nodes. A valid license is required, and a trial license is available on request. Mirantis offers 24/7 proactive support or managed services.