Learning Journey: Part 05 of 16 Module Goal: Build a clear operational mental model of clusterctl: understand its precise architectural boundary against continuous reconciliation, manage provider lifecycles, render workload cluster manifests, inspect object trees, and pivot management cluster state. Target Spec: Cluster API v1.14 (v1beta2 APIs). Prerequisites: Part 04: Building Your First Cluster API Environment. 1. The Core Boundary: CLI Tooling vs. Continuous Reconciliation In Part 04, we used clusterctl to initialize a local management cluster and render a workload cluster manifest....

Learning Journey: Part 04 of 16 Module Goal: Build a local Cluster API management environment using kind and the Docker infrastructure provider (CAPD), observe real-time custom resource expansion, and trace declarative cluster reconciliation. Target Spec: Cluster API v1.14 (v1beta2 APIs). Prerequisites: Part 03: Cluster API Object Model: Mapping the Custom Resource Graph (Three-layer resource model, contract references, and template blueprints). 1. The Hands-On Objective: Grounding Abstractions in Real State In Parts 01 through 03, we established the core concepts of Cluster API (CAPI): declarative reconciliation, management versus workload cluster separation, and the three-layer object graph (Cluster, ControlPlane, MachineDeployment)....

Learning Journey: Part 03 of 16 Module Goal: Master the complete Cluster API object graph: how Cluster, Machine, MachineSet, MachineDeployment, MachinePool, KubeadmControlPlane, BootstrapConfig, and Infrastructure resources fit together without getting lost in CRD overload. Target Spec: Cluster API v1.14 (v1beta2 APIs). Prerequisites: Part 02: Cluster API Architecture: How the Control Plane Pieces Cooperate. 1. Why Are There So Many Objects? When you first start with Cluster API (CAPI), running kubectl get crds in your management cluster can feel overwhelming....