projects:crunchy:picocluster:start
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
projects:crunchy:picocluster:start [2022/11/22 15:36] – [Info Source 2: Alex Ortner, Medium: How to build a Raspberry Pi Kubernetes Cluster with k3s] rolf001 | projects:crunchy:picocluster:start [2022/12/02 00:41] – [Result: RUNNING!] rolf001 | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ~~NOTOC~~ | ||
====== PicoCluster Installation ====== | ====== PicoCluster Installation ====== | ||
- | We decided to replace the preinstalled OS of the Pis in the cluster | + | We decided to replace the preinstalled OS of the Pis in the pre-built PicoCluster |
Line 161: | Line 162: | ||
| Jeff Geerling | | | Jeff Geerling | | ||
- | **GIT REPO**: https:// | + | **:!: K3s Ansible Git Repository:** https:// |
+ | This is what I am using, with a few adaptations (names, IP adresses, etc.) | ||
==== Info Source 2: Alex Ortner, Medium: How to build a Raspberry Pi Kubernetes Cluster with k3s ==== | ==== Info Source 2: Alex Ortner, Medium: How to build a Raspberry Pi Kubernetes Cluster with k3s ==== | ||
Line 170: | Line 172: | ||
| {{https:// | | {{https:// | ||
- | The figure above shows the rough outline | + | The figure above gives a rough overview |
- | **I decided to install client and master in parallel on one Raspberry Pi!** | + | |
+ | **:!: Modification: | ||
==== Info Source 3: Cyprien Lecallier, Padok: K3S with Raspberry Pi: configuration, | ==== Info Source 3: Cyprien Lecallier, Padok: K3S with Raspberry Pi: configuration, | ||
Line 198: | Line 201: | ||
I decided to use **Snap Store** as described on the // | I decided to use **Snap Store** as described on the // | ||
+ | |||
+ | ==== Some kubectl Tests ==== | ||
+ | |||
+ | |||
+ | |||
+ | ===== Result: RUNNING! ===== | ||
+ | |||
+ | I can deploy first examples. Now I would need to learn more about **kubectl.** | ||
+ | |||
+ | < | ||
+ | sudo kubectl get nodes | ||
+ | |||
+ | sudo kubectl get pods --all-namespaces | ||
+ | |||
+ | sudo kubectl get pods -A | ||
+ | |||
+ | sudo kubectl run nginx-sample --image=nginx --port=80 | ||
+ | |||
+ | sudo kubectl get pods -A | ||
+ | |||
+ | kubectl delete pod nginx-sample | ||
+ | |||
+ | sudo kubectl get pods -A | ||
+ | </ | ||
+ | ===== Summary / Outlook ===== | ||
+ | |||
+ | * The most important info for me was the **K3s Ansible** project described above together with the **matching video by Jeff Geerling.** \\ Both resources are referred to as "Info Source 1" above. | ||
+ | |||
+ | **Improvements**\\ | ||
+ | What I would improve in the next development cycle: | ||
+ | * Separate the client node from the K3s master node: | ||
+ | * 1x " | ||
+ | * 1x K3s master node: minimal OS, no GUI | ||
+ | * 3x K3s worker nodes: minimal OS, no GUI | ||
+ | |||
+ | |||
+ | |||
projects/crunchy/picocluster/start.txt · Last modified: 2022/12/02 00:48 by rolf001