Merge pull request #1 from jplandolt/multi-worker

Multi workers

Author: TryToLearnProgramming

README.md

@@ -5,14 +5,14 @@
 [![Kubernetes](https://img.shields.io/badge/kubernetes-%23326ce5.svg?style=for-the-badge&logo=kubernetes&logoColor=white)](https://kubernetes.io/)
 [![Ubuntu](https://img.shields.io/badge/Ubuntu-E95420?style=for-the-badge&logo=ubuntu&logoColor=white)](https://ubuntu.com/)
 
-This project sets up a local Kubernetes cluster using Vagrant and VirtualBox. It creates two Ubuntu 22.04 virtual machines: one master node and one worker node with automatic installation of Docker, Kubernetes components, and necessary configurations.
+This project sets up a local Kubernetes cluster using Vagrant and VirtualBox. It creates two Ubuntu 24.04 virtual machines: one control plane node and one worker node with automatic installation of Docker, Kubernetes components, and necessary configurations.
 
 ## Architecture
 
 ```mermaid
 graph TB
     subgraph Vagrant-Managed Environment
-        subgraph Master Node
+        subgraph Control Plane Node
             A[Control Plane] --> B[API Server]
             B --> C[etcd]
             B --> D[Controller Manager]
@@ -25,7 +25,7 @@ graph TB
         B <-.-> F
         B <-.-> H
     end
-    style Master Node fill:#f9f,stroke:#333,stroke-width:2px
+    style Control Plane Node fill:#f9f,stroke:#333,stroke-width:2px
     style Worker Node fill:#bbf,stroke:#333,stroke-width:2px
 ```
 
@@ -45,7 +45,7 @@ graph TB
 <table>
 <tr>
     <td align="center">🔄</td>
-    <td>Automated VM provisioning with Ubuntu 22.04</td>
+    <td>Automated VM provisioning with Ubuntu 24.04</td>
 </tr>
 <tr>
     <td align="center">🌐</td>
@@ -71,19 +71,19 @@ graph TB
 
 ## 🖥 Cluster Configuration
 
-> **Note about IP Addressing**: This configuration uses `192.168.63.1` and `192.168.63.2` for the master and worker nodes respectively. You can modify these IPs in the `Vagrantfile` to use any IP addresses from your router's IP range that are outside the DHCP scope. Make sure to choose IPs that won't conflict with other devices on your network.
+> **Note about IP Addressing**: This configuration uses `192.168.63.11` and `192.168.63.12` for the control plane and worker nodes respectively. You can modify these IPs in the `Vagrantfile` to use any IP addresses from your router's IP range that are outside the DHCP scope. Make sure to choose IPs that won't conflict with other devices on your network.
 
 <table>
 <tr>
-    <th width="50%">Master Node</th>
+    <th width="50%">Control Plane Node</th>
     <th width="50%">Worker Node</th>
 </tr>
 <tr>
 <td>
 
 ```yaml
-IP: 192.168.63.1
-Hostname: master
+IP: 192.168.63.11
+Hostname: cplane
 Memory: 2048MB
 CPUs: 2
 Role: Control Plane
@@ -93,7 +93,7 @@ Role: Control Plane
 <td>
 
 ```yaml
-IP: 192.168.63.2
+IP: 192.168.63.12
 Hostname: worker
 Memory: 2048MB
 CPUs: 2
@@ -110,7 +110,7 @@ Role: Worker
 
 ## Quick Start
 
-> **💡 Tip**: Before starting, you may want to adjust the IP addresses in the `Vagrantfile` if the default IPs (`192.168.63.1, 192.168.63.2`) conflict with your network setup. Edit the `private_network` IP settings in the Vagrantfile to match your network requirements.
+> **💡 Tip**: Before starting, you may want to adjust the IP addresses in the `Vagrantfile` if the default IPs (`192.168.63.11, 192.168.63.12`) conflict with your network setup. Edit the `private_network` IP settings in the Vagrantfile to match your network requirements.
 
 1. Clone this repository:
 ```bash
@@ -123,9 +123,9 @@ cd vagrant
 vagrant up
 ```
 
-3. SSH into the master node:
+3. SSH into the control plane node:
 ```bash
-vagrant ssh master
+vagrant ssh cplane
 ```
 
 4. SSH into the worker node:
@@ -163,11 +163,11 @@ vagrant destroy
 
 After the VMs are up and running, follow these steps to initialize your Kubernetes cluster:
 
-### 1. On Master Node
+### 1. On Control Plane Node
 
-First, log into the master node:
+First, log into the control plane node:
 ```bash
-vagrant ssh master
+vagrant ssh cplane
 ```
 
 Pull required Kubernetes images:
@@ -177,7 +177,7 @@ sudo kubeadm config images pull
 
 Initialize the cluster:
 ```bash
-sudo kubeadm init --pod-network-cidr=10.201.0.0/16 --apiserver-advertise-address=192.168.63.1
+sudo kubeadm init --pod-network-cidr=10.201.0.0/16 --apiserver-advertise-address=192.168.63.11
 ```
 
 ### 2. Install CNI (Container Network Interface)
@@ -187,13 +187,33 @@ After the cluster initialization, install Weave CNI:
 kubectl apply -f https://github.com/weaveworks/weave/releases/download/v2.8.1/weave-daemonset-k8s.yaml
 ```
 
+### NOTE: Control Plane script 'cluster_init.sh' wraps steps 1. and 2.
+
+For ease of use, a single script `cluster_init.sh` was created as a function of the "vagrant up" command for the control plane(s) that performs all of the above steps:
+* k8s image pull
+* kubeadm init
+* local copy of "kube config"
+* Weave CNI install
+
+and can be run with the vagrant command:
+```bash
+vagrant ssh cplane -c "./cluster_init.sh"
+```
+
 ### 3. Join Worker Node
 
-Copy the `kubeadm join` command from the master node's initialization output and run it on the worker node with sudo privileges.
+Copy the `kubeadm join` command from the control plane node's initialization output and run it on the worker node with sudo privileges.
+
+### NOTE: Control Plane script 'join_cmd.sh' shows the 'join' command
+
+For ease of use, script `join_cmd.sh` was created to display the join command for use on worker nodes with this vagrant command:
+```bash
+vagrant ssh cplane -c "./join_cmd.sh"
+```
 
 ### 4. Verify Cluster Status
 
-After joining the worker node, verify the cluster status from the master node:
+After joining the worker node, verify the cluster status from the control plane node:
 
 ```bash
 # Check node status
@@ -203,7 +223,7 @@ kubectl get nodes
 Expected output (it may take a few minutes for the nodes to be ready):
 ```
 NAME     STATUS   ROLES           AGE     VERSION
-master   Ready    control-plane   5m32s   v1.30.x
+cplane   Ready    control-plane   5m32s   v1.30.x
 worker   Ready    <none>          2m14s   v1.30.x
 ```
 
@@ -228,7 +248,7 @@ sudo systemctl restart containerd
 sudo systemctl daemon-reload
 ```
 
-3. After cleanup, retry the cluster initialization on master and join command on worker.
+3. After cleanup, retry the cluster initialization on the cplane and join command on worker.
 
 ## Default Credentials