projects:crunchy:picocluster:start
Differences
This shows you the differences between two versions of the page.
| projects:crunchy:picocluster:start [2022/11/23 19:58] – rolf001 | projects:crunchy:picocluster:start [2023/01/05 14:38] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 2: | Line 2: | ||
| ====== 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 162: | 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 173: | Line 174: | ||
| The figure above gives a rough overview of the planned architecture. | The figure above gives a rough overview of the planned architecture. | ||
| - | **:!: Modification: | + | **:!: Modification: |
| ==== Info Source 3: Cyprien Lecallier, Padok: K3S with Raspberry Pi: configuration, | ==== Info Source 3: Cyprien Lecallier, Padok: K3S with Raspberry Pi: configuration, | ||
| Line 200: | 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 ==== | ||
| + | |||
| + | https:// | ||
| + | |||
| + | |||
| + | < | ||
| + | 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 | ||
| + | |||
| + | #sudo kubectl expose deployment/ | ||
| + | |||
| + | #sudo kubectl expose nginx-sample --type=" | ||
| + | |||
| + | kubectl delete pod nginx-sample | ||
| + | |||
| + | sudo kubectl get pods -A | ||
| + | </ | ||
| + | |||
| + | ===== Result: RUNNING! ===== | ||
| + | |||
| + | I can deploy first examples. Now I would need to learn more about **kubectl.** | ||
| + | |||
| + | |||
| + | ===== 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.1669229927.txt.gz · Last modified: 2023/01/05 14:38 (external edit)