canonical/microk8s

MicroK8s is a small, fast, single-package Kubernetes for datacenters and the edge.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 9 minutes ago
Added to GitGenius on September 7th, 2026
Created on May 9th, 2018
Open Issues & Pull Requests: 161 (+0)
GitHub issues: Enabled
Number of forks: 836
Total Stargazers: 9,367 (+0)
Total Subscribers: 105 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Issue API getrepoissuespagesummary failed: 429 Rate limit exceeded. Please try again later.

Detailed Description

MicroK8s is a lightweight Kubernetes distribution that runs as a single package on Linux systems, designed for developer workstations, edge computing, IoT devices, and CI/CD pipelines.

The project addresses the need for a minimal, self-contained Kubernetes installation that eliminates complex setup and dependency management. Rather than requiring multiple components and extensive configuration, MicroK8s bundles a fully conformant Kubernetes cluster with all dependencies included in a single snap package. This approach works across numerous Linux distributions and provides immediate access to a production-compatible Kubernetes environment without the operational overhead of managing separate services.

Developers should choose MicroK8s when they need a fast, low-friction way to run Kubernetes locally or on resource-constrained environments. It suits laptop development, edge deployments, and scenarios where simplicity matters more than cluster scale. The tool includes a curated collection of optional add-ons covering service meshes like Istio and Linkerd, serverless platforms like Knative, monitoring stacks with Prometheus and Grafana, and infrastructure components such as DNS, ingress controllers, and dashboards. Security updates are available for all reported issues and can be applied immediately or scheduled according to maintenance requirements. The distribution tracks upstream Kubernetes releases closely, making beta, release candidate, and final versions available on the same day as upstream, while also supporting all Kubernetes versions from 1.10 onwards.

Development activity shows consistent engagement with the upstream Kubernetes project, maintaining feature parity with each release cycle. The project maintains active security patching practices and provides clear documentation for both users and contributors. The codebase reflects ongoing refinement of the snap-based distribution model and the add-on ecosystem, with build instructions available for those wishing to contribute modifications or extensions.