MicroK8s is a lightweight, single-package Kubernetes distribution distributed as a snap. It bundles upstream Kubernetes components (kube-apiserver, kubelet, etcd, containerd, runc, flannel, Calico CNI, dqlite, Helm) into a single snap package with a unified 'kubelite' binary that runs all control plane services as threads. The system provides a CLI (microk8s) with subcommands for cluster management (enable/disable addons, join/leave cluster, status, reset, upgrade), and an addon system that allows installing additional services (e.g., dashboard, ingress, registry) via git-cloned repositories with executable enable/disable hooks. The architecture is a monolith packaged as a snap, with services managed by snap daemons and configuration stored in snap data directories. Key entry points include the snap hooks (configure, install, remove), wrapper scripts in scripts/wrappers/ (enable.py, disable.py, join.py, status.py, etc.), and the kubelite binary. External dependencies include the snap runtime, upstream Kubernetes binaries, containerd, runc, etcd, dqlite, flanneld, and various CNI plugins. The build system uses pinned component versions with patch management for each Kubernetes release, and upgrade scripts handle migrations between versions with rollback support.
Pangee Cluster is a graphical tool for offline Kubernetes cluster lifecycle management, including installation, upgrade, backup, node operations, and SSH access. The backend is a Go REST API (Gin) that orchestrates Ansible playbooks from versioned resource packages. The frontend is a Vue 3 single-page application (with some legacy Vue 2 patterns) that provides a comprehensive UI for cluster planning, operation execution, real-time log tailing, and SSH terminal. The tool is primarily designed for air-gapped environments where clusters are provisioned from pre-packaged resource bundles containing Kubernetes binaries, container runtimes, and Ansible roles. Despite its functional breadth, the codebase shows signs of technical debt: mixed Vue API styles, heavy mixins, no test suite, and tight coupling to a custom-patched Ansible version. The resource package abstraction and generic form editing components are notable for reusability, but overall the architecture is typical of a production tool that has evolved organically rather than being designed for clean reuse.