MicroShift vs vCluster Platform

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.

vCluster Platform is a management plane for deploying, configuring, and operating tenant cluster fleets through a web UI, CLI, and API. It manages tenants across EKS, GKE, AKS, bare metal, and private cloud, with isolated tenant clusters and shared-node, dedicated-node, private-node, Auto Nodes, and Standalone tenancy models. With vCluster Cloud, the platform is hosted while host and virtual clusters remain in the customer's infrastructure; self-hosted deployment puts the full platform there. The Free plan is free and permits unlimited virtual clusters within a limit of 64 CPUs or 32 GPUs, with a maximum of one HA vCluster. It also supports provisioning, multi-cluster management, policy enforcement, and upgrade management. Listed integrations include Terraform, Rancher, Argo CD, HashiCorp Vault, and Istio. Enterprise features include SSO, audit logging, vulnerability alerts, security review, FIPS-compliant images, enterprise support, and SLAs. One isolation caveat is that shared nodes share several underlying components across tenants, including the kernel, kubelet, node filesystem, and host network. The maker describes use by AI cloud providers and public and private cloud teams.