You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the shutdown of Weaveworks, Weave CNI has been effectively discontinued, the GitHub repo archived in June 2024. So a new CNI should be considered, and the first suggestion is Flannel
### NOTE: Control Plane script 'cluster_init.sh' wraps steps 1. and 2.
191
212
192
213
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:
> **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`.
231
252
253
+
### 5. (Optional) Set Role for Worker Node(s)
254
+
255
+
As the output above shows, there is no initial role set for worker nodes. You can set their role to "worker" with:
256
+
257
+
The Kubernetes Dashboard is Web UI that allows you to manage your cluster; configure and manage aspects of the system, troubleshoot, and to have an overview of applications running on your cluster
258
+
259
+
```bash
260
+
vagrant ssh cplane -c "./set_worker_role.sh"
261
+
```
262
+
263
+
This script can be run any time a new node is added.
The Kubernetes Dashboard is Web UI that allows you to manage your cluster; configure and manage aspects of the system, troubleshoot, and to have an overview of applications running on your cluster
268
+
269
+
First, log into the control plane node:
270
+
```bash
271
+
vagrant ssh cplane
272
+
```
273
+
274
+
Execute the Dashboard setup script:
275
+
```bash
276
+
./kub_dashboard.sh <option>
277
+
```
278
+
279
+
Where `<option>` is one of:
280
+
* worker - to deploy dashboard on any worker node
281
+
* cplane - to deploy dashboard on the control plane
282
+
* token - to show the dashboard credentials token (and the dashboard url)
283
+
284
+
Normally, the Kubernetes Dashboard would be deployed to one of the worker nodes. This would always be the case in a production
285
+
Kubernetes cluster. However for a small development cluster, it doesn't hurt to run the dashboard on the control plane
286
+
232
287
### Troubleshooting
233
288
234
289
If you encounter issues while joining the worker node, try these steps on both nodes:
echo "deb [signed-by=/usr/share/keyrings/helm.gpg] https://packages.buildkite.com/helm-linux/helm-debian/any/ any main" | sudo tee /etc/apt/sources.list.d/helm-stable-debian.list
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.
9
+
10
+
## Bash Scripts
11
+
12
+
These scripts are to make it easy to bring up and maintain the Kubernetes Cluster. Some are collections of manual provisioning commands from the original project (which reduces manual typing errors). Others are facilitators, to manage the Control Plane and Worker nodes in an easy and repeatable fashion.
13
+
14
+
<table>
15
+
<tr>
16
+
<td>🚜 Provision</td>
17
+
<td>Package Installation and Service Management of Machines</td>
18
+
</tr>
19
+
<tr>
20
+
<td>🚀 Cplane</td>
21
+
<td>To spin up and manage the Control Plane</td>
22
+
</tr>
23
+
<tr>
24
+
<td>🛠 Worker</td>
25
+
<td>To join up and manage the Worker nodes</td>
26
+
</tr>
27
+
</table>
28
+
29
+
## License
30
+
31
+
This project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details.
0 commit comments