harikubeadm Playground

HariKubeadm

HariKube replaces the local etcd instance with an etcd-compatible middleware backed by SQLite. This playground gives you the patched images and kubeadm wiring, but it leaves cluster creation up to you.

System Components

• kubeadm: Cluster lifecycle management and bootstrapping
• kubelet: Runs static pods and regular workloads on the node
• containerd: Container runtime used by kubelet
• HariKube middleware: etcd-compatible storage endpoint backed by SQLite
• kubectl (alias: k): Kubernetes cluster management and debugging

Versions

• Kubernetes: v1.35.0
• HariKube middleware: release-v1.0.3

Getting Started

This playground preloads the patched HariKube control-plane images and the middleware image during the build.

Initialize the cluster on the harikubeadm machine:

/opt/lab/init.sh --remove-taint

Then configure kubectl access on the dev-machine:

/opt/lab/configure.sh

What Changes Here?

• kubeadm uses HariKube as its external storage endpoint
• kubeadm skips its own etcd phase and uses a HariKube-backed etcd static pod instead
• kube-apiserver and kube-controller-manager are replaced with HariKube images
• HariKube itself runs as a static pod managed by kubelet
• cluster state is persisted in /var/lib/harikube/k8s.sqlite

Learn More

• HariKube
  • Overview
  • Installation
• Kubernetes
  • kubeadm
  • Customizing components with kubeadm

Happy learning!