Edge Kubernetes & Zero-Touch Provisioning›Foundations · Cheat sheet & self-check

Foundations · wrap-up

Cheat sheet & self-check

Every command from this section on one page.

01 · Why ZTP for edge

The ZTP promise

Rack, cable, power onThe only hands-on work at the site
BMC/PXE → OS → Kubernetes → workloadsEverything else automated and remote
Site definition in GitHardware inventory + cluster spec + workloads

Lifecycle

Day 0Design, inventory, images, site definition
Day 1Provision: bare metal → cluster → apps
Day 2Upgrade, scale, repair, rebuild, retire

02 · Architecture for edge ZTP

Planes

Management plane (central)Git, registries, cluster lifecycle controllers, observability
Provisioning at the siteDHCP/TFTP/HTTP boot + BMC access: needs L2 or DHCP relay
Workload clusters (per site)Run the applications; pull config and images

Site networks

BMC / OOB VLANRedfish/IPMI; isolated, no internet
Provisioning VLANPXE/iPXE, DHCP; can be the node network
Node / cluster networkKubernetes API VIP, node IPs
Workload / uplinkServices, backhaul to the centre

03 · Cluster sizing for edge

Shapes

1 nodeNo HA; cheapest; a node failure = site outage
3 nodes, compact (CP + workloads on all)Tolerates 1 node failure; common edge default
3 CP + N workersMore isolation and capacity; more hardware
2 nodesNo etcd fault tolerance without an external witness

Settings

kubectl taint nodes <n> node-role.kubernetes.io/control-plane:NoSchedule-Allow workloads on control-plane nodes (compact)
kubelet: systemReserved / kubeReserved / evictionHardProtect the OS and kubelet from workloads
etcd quorum = floor(n/2) + 13 members → survives 1 failure