OPERATING DOCUMENT / KUBE-READY-BOX

System Architecture

Build architecture and product boundary from Ubuntu cloud images to verified Kubernetes-ready Vagrant boxes.

01 / Context02 / Procedure03 / Operations04 / Verification

System Architecture

The Kube Ready Box product boundary is a verified OS image. A container runtime, Kubernetes, kubeadm/kubelet/kubectl, and a CNI are not bundled; the consuming cluster project installs them.

Repository layers

LayerResponsibility
Packer definitionUbuntu release, AMD64/ARM64, VirtualBox/VMware, and ext4/XFS matrix
OS contractkernel modules, sysctl, limits, packages, and boot-time disk expansion
Capability modulesnetwork, storage, security, time-sync, and observability readiness
Verificationprovider boot tests and machine-readable tuning evidence
Release evidencetrace validated provider artifacts and their build inputs

Invariants

  • Kubernetes-ready is distinct from Kubernetes-preinstalled.
  • ext4 and XFS remain separate artifacts because their behavior differs.
  • AMD64 and ARM64 follow one OS contract with documented provider exceptions.
  • Template validation does not replace real VM runtime evidence.
DOCUMENT TRACE

Return to the project record to see architecture, development pulse, proof and related field notes in one context.