Add .gitignore, LICENSE, and update README with project details and instructions

Your Name · Your Name · commit 2913837422b0 · 2025-05-11T15:19:11.000+05:30
diff --git a/.gitignore b/.gitignore
@@ -0,0 +1,27 @@
+# Vagrant specific
+.vagrant/
+*.log
+
+# Virtual machine files
+*.box
+*.vdi
+*.vmdk
+*.vhd
+
+# OS specific files
+.DS_Store
+Thumbs.db
+
+# Environment files
+.env
+*.env
+
+# IDE specific files
+.vscode/
+.idea/
+*.swp
+*.swo
+
+# Temporary files
+*.tmp
+*~
diff --git a/LICENSE b/LICENSE
@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2024 Vagrant Kubernetes Cluster
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
diff --git a/README.md b/README.md
@@ -1 +1,255 @@
-# vagrant
+# Vagrant Kubernetes Cluster
+
+[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
+[![Vagrant](https://img.shields.io/badge/vagrant-%231563FF.svg?style=for-the-badge&logo=vagrant&logoColor=white)](https://www.vagrantup.com/)
+[![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.
+
+## Architecture
+
+```mermaid
+graph TB
+    subgraph Vagrant-Managed Environment
+        subgraph Master Node
+            A[Control Plane] --> B[API Server]
+            B --> C[etcd]
+            B --> D[Controller Manager]
+            B --> E[Scheduler]
+        end
+        subgraph Worker Node
+            F[kubelet] --> G[Container Runtime]
+            H[kube-proxy] --> G
+        end
+        B <-.-> F
+        B <-.-> H
+    end
+    style Master Node fill:#f9f,stroke:#333,stroke-width:2px
+    style Worker Node fill:#bbf,stroke:#333,stroke-width:2px
+```
+
+![Cluster Network](https://raw.githubusercontent.com/kubernetes/kubernetes/master/logo/logo.png)
+
+## Prerequisites
+
+- [VirtualBox](https://www.virtualbox.org/wiki/Downloads)
+- [Vagrant](https://www.vagrantup.com/downloads)
+- At least 4GB of RAM available
+- At least 20GB of free disk space
+
+## ✨ Features
+
+<table>
+<tr>
+    <td align="center">🔄</td>
+    <td>Automated VM provisioning with Ubuntu 22.04</td>
+</tr>
+<tr>
+    <td align="center">🌐</td>
+    <td>Pre-configured network settings</td>
+</tr>
+<tr>
+    <td align="center">🐳</td>
+    <td>Automatic installation of Docker and Kubernetes components</td>
+</tr>
+<tr>
+    <td align="center">🚀</td>
+    <td>Ready-to-use Kubernetes cluster setup</td>
+</tr>
+<tr>
+    <td align="center">🔒</td>
+    <td>Secure communication between nodes</td>
+</tr>
+<tr>
+    <td align="center">🔍</td>
+    <td>Easy monitoring and management</td>
+</tr>
+</table>
+
+## 🖥 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.
+
+<table>
+<tr>
+    <th width="50%">Master Node</th>
+    <th width="50%">Worker Node</th>
+</tr>
+<tr>
+<td>
+
+```yaml
+IP: 192.168.63.1
+Hostname: master
+Memory: 2048MB
+CPUs: 2
+Role: Control Plane
+```
+
+</td>
+<td>
+
+```yaml
+IP: 192.168.63.2
+Hostname: worker
+Memory: 2048MB
+CPUs: 2
+Role: Worker
+```
+
+</td>
+</tr>
+</table>
+
+![Cluster Diagram](https://d33wubrfki0l68.cloudfront.net/2475489eaf20163ec0f54ddc1d92aa8d4c87c96b/e7c81/images/docs/components-of-kubernetes.svg)
+
+## 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.
+
+1. Clone this repository:
+```bash
+git clone <repository-url>
+cd vagrant
+```
+
+2. Start the cluster:
+```bash
+vagrant up
+```
+
+3. SSH into the master node:
+```bash
+vagrant ssh master
+```
+
+4. SSH into the worker node:
+```bash
+vagrant ssh worker
+```
+
+5. Stop the cluster:
+```bash
+vagrant halt
+```
+
+6. Destroy the cluster:
+```bash
+vagrant destroy
+```
+
+## 🛠 Components Installed
+
+<details>
+<summary>Click to expand installed components</summary>
+
+| Component | Version | Description |
+|-----------|---------|-------------|
+| Docker CE | Latest | Container runtime engine |
+| kubelet | Latest | Node agent |
+| kubeadm | Latest | Cluster bootstrapping tool |
+| kubectl | Latest | Command-line interface |
+| containerd | Latest | Container runtime |
+| Weave CNI | v2.8.1 | Container Network Interface |
+
+</details>
+
+## Cluster Setup Instructions
+
+After the VMs are up and running, follow these steps to initialize your Kubernetes cluster:
+
+### 1. On Master Node
+
+First, log into the master node:
+```bash
+vagrant ssh master
+```
+
+Pull required Kubernetes images:
+```bash
+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
+```
+
+### 2. Install CNI (Container Network Interface)
+
+After the cluster initialization, install Weave CNI:
+```bash
+kubectl apply -f https://github.com/weaveworks/weave/releases/download/v2.8.1/weave-daemonset-k8s.yaml
+```
+
+### 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.
+
+### 4. Verify Cluster Status
+
+After joining the worker node, verify the cluster status from the master node:
+
+```bash
+# Check node status
+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
+worker   Ready    <none>          2m14s   v1.30.x
+```
+
+> **Note**: The nodes may show `NotReady` status initially as the CNI (Container Network Interface) is being configured. Please wait a few minutes for the status to change to `Ready`.
+
+### Troubleshooting
+
+If you encounter issues while joining the worker node, try these steps on both nodes:
+
+1. Reset the cluster configuration:
+```bash
+sudo kubeadm reset
+```
+
+2. Perform system cleanup:
+```bash
+sudo swapoff -a
+sudo systemctl restart kubelet
+sudo iptables -F
+sudo rm -rf /var/lib/cni/
+sudo systemctl restart containerd
+sudo systemctl daemon-reload
+```
+
+3. After cleanup, retry the cluster initialization on master and join command on worker.
+
+## Default Credentials
+
+- Username: vagrant
+- Password: vagrant
+
+## License
+
+This project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details.
+
+Copyright (c) 2024 Vagrant Kubernetes Cluster
+
+## 📫 Support & Contribution
+
+If you encounter any issues or need assistance:
+
+[![Create Issue](https://img.shields.io/badge/Create-Issue-green.svg)](https://github.com/yourusername/vagrant-kubernetes/issues/new)
+[![Pull Request](https://img.shields.io/badge/Pull-Request-blue.svg)](https://github.com/yourusername/vagrant-kubernetes/pulls)
+
+## 📝 License
+
+This project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details.
+
+---
+
+<div align="center">
+Made with ❤️ for the Kubernetes community
+</div>
diff --git a/instructions.txt b/instructions.txt
@@ -1,13 +1,14 @@
-TO SPEED UP THE PROCESS 1ST RUN -
-sudo kubeadm config images pull
+TO SPEED UP THE PROCESS 1ST RUN in the master NODE-
+- sudo kubeadm config images pull
 
-TO INIT, RUN -
-sudo kubeadm init --pod-network-cidr=10.201.0.0/16 --apiserver-advertise-address=192.168.63.1
+TO INIT, RUN  in the master NODE-
+- sudo kubeadm init --pod-network-cidr=10.201.0.0/16 --apiserver-advertise-address=192.168.63.1
+- you wull get a kubeadm join command run that in you master node after Install the CNI
 
 TO INSTALL CNI (weave) -
-kubectl apply -f https://github.com/weaveworks/weave/releases/download/v2.8.1/weave-daemonset-k8s.yaml
+- kubectl apply -f https://github.com/weaveworks/weave/releases/download/v2.8.1/weave-daemonset-k8s.yaml
 
-IF face proble while jioning worker node -
+IF face proble while jioning worker node, reatart master node and run below commands-
 sudo kubeadm reset
 
 sudo swapoff -a => all nodes.
