Differences

This shows you the differences between two versions of the page.

--- projects:crunchy:picocluster:start [2022/11/23 20:02] – [Info Source 1] rolf001
+++ projects:crunchy:picocluster:start [2023/01/05 14:38] (current) – external edit 127.0.0.1
@@ Line 162: / Line 162: @@
 | Jeff Geerling |
-**:!: K3s Ansible Git Repository**: https://github.com/k3s-io/k3s-ansible \\
+**:!: K3s Ansible Git Repository:** https://github.com/k3s-io/k3s-ansible \\
 This is what I am using, with a few adaptations (names, IP adresses, etc.)
@@ Line 174: / Line 174: @@
 The figure above gives a rough overview of the planned architecture.
-**:!: Modification: I decided to install client and master in parallel on one Raspberry Pi!**
+**:!: Modification: I decided to install client and master in parallel on one Raspberry Pi (the mater node)!**
 ==== Info Source 3: Cyprien Lecallier, Padok: K3S with Raspberry Pi: configuration, connection and installation ====
@@ Line 201: / Line 201: @@
 I decided to use **Snap Store** as described on the //snapcraft.io// webpage **Install kubectl on Raspberry Pi using the Snap Store:** \\ https://snapcraft.io/install/kubectl/raspbian
+==== Some kubectl Tests ====
+https://www.tecmint.com/deploy-nginx-on-a-kubernetes-cluster/
+<code>
+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/nginx-sample --type="NodePort" --port 80
+#sudo kubectl expose nginx-sample --type="NodePort" --port 80
+kubectl delete pod nginx-sample  --now
+sudo kubectl get pods -A
+</code>
+===== 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 "client" node: OS with GUI, Ansible master, kubectl
+    * 1x K3s master node: minimal OS, no GUI
+    * 3x K3s worker nodes: minimal OS, no GUI