Edge Kubernetes & Zero-Touch Provisioning
Zero-touch provisioning for edge Kubernetes using open-source tooling: Redfish and PXE to boot, Tinkerbell or Metal3 to provision, EKS Anywhere or RKE2 to form the cluster, and GitOps to manage the fleet, all without internet access.
What you'll be able to do
- Design a ZTP flow from BMC to a Ready node
- Build immutable OS images and serve them offline
- Operate a fleet of small clusters with GitOps
Before you start
Linux — Level by Level (Level 2), Kubernetes Administration Level 2.
How it works
Each lesson: plain-language idea → how it really works → hands-on. Each section ends with a cheat sheet & self-check.
Curriculum
Lessons marked “Read” are ready; the rest are on the way.
Foundations
- 01Why ZTP for edgeTruck rolls, scale, consistencyRead →
- 02Architecture for edge ZTPManagement cluster, sites, trust boundariesRead →
- 03Cluster sizing for edgeSingle-node, 3-node compact, small HARead →
- 📋Cheat sheet & self-checkEvery command from this section on one page, then 9 questions to check yourself.Open →
Provisioning
- 04Bare-metal provisioningRedfish, IPMI, PXE/iPXE, DHCPRead →
- 05Tinkerbell & Metal3Workflows, hardware inventory, BareMetalHostRead →
- 06OS image creationImmutable images: ISO, RAW, QCOW2, cloud-initRead →
- 07Air-gapped deliveryHarbor mirrors, offline charts, signed bundlesRead →
- 📋Cheat sheet & self-checkEvery command from this section on one page, then 12 questions to check yourself.Open →
Cluster & Fleet
- 08EKS Anywhere on bare metalCluster spec, lifecycle, upgradesRead →
- 09Rancher + RKE2 provisioningHardened defaults, SUSE SLE MicroRead →
- 10GitOps fleet managementOne repo, hundreds of sitesRead →
- 11Edge networking, storage & securityThe constraints that differ at the edgeRead →
- 12DR & compliance at scaleRebuild a site from GitRead →
- 📋Cheat sheet & self-checkEvery command from this section on one page, then 15 questions to check yourself.Open →
Real-world scenarios
Work through each one: symptom → misleading signal → evidence → root cause → prevention.
DHCP, VLAN tagging or the boot image? Isolate the layer.
Firmware and BIOS drift across hardware batches.
Boot ordering, etcd quorum and time sync.
This site is a public version of my personal engineering knowledge hub. It intentionally excludes confidential company information and internal operational details.