How eryx0/fanapcampus-ansible-kubeadm works
Main Components
• Ansible Playbook: At the top level, you have a playbook (playbook.yaml) that orchestrates the execution of various roles.
• Roles/Modules: The project contains several specially named directories:
• prerequisites – likely handling the installation of necessary packages and ensuring system preconditions.
• cluster-init – responsible for beginning the cluster initialization process.
• kubeadm – managing the core kubeadm commands to actually create or bootstrap the Kubernetes control plane.
• node-join – for roles where worker nodes join the initialized Kubernetes cluster.
• Ancillary Files: Each role has its own README, meta, and tasks directories that define metadata (like dependencies or variables) and the specific steps (tasks) to run.
Component Interactions
• Prerequisites
• Cluster Initialization (cluster-init)
• Kubeadm execution (kubeadm)
• Node joining (node-join)
• That the “prerequisites” role must complete before the cluster initialization begins.
Architectural Patterns and Design Principles
• Modularity: Emphasize that each role (prerequisites, cluster-init, kubeadm, node-join) encapsulates a focused set of responsibilities.
• Sequential Flow: Illustrate the dependency and sequential order (likely prerequisites → cluster-init → kubeadm → node-join) as these steps must occur in order to successfully initialize the Kubernetes cluster.
• Reusability & Extensibility: Mention that the roles’ separation via individual directories and task files allows for easy updates or extensions.
Relevant Technologies
• Ansible: The backbone for task orchestration.
• Kubeadm: The tool used for bootstrapping the Kubernetes cluster.
• Kubernetes: The ultimate target system.
• YAML: The configuration format (as seen in all task files and playbooks).