docs: update hardware documentation

README.md

@@ -11,37 +11,10 @@ Please have a look into the documentation
 ## Hardware
 
 I use a cluster of seven Raspberry PIs. Three for the controlplane and the other
-four as worker nodes. Each of the worker nodes has a 2 TB SSD used for longhorn.
+four as worker nodes. After some time added two small Lenovo Thinkcentres inspired
+by [TinyMiniMicro](https://www.servethehome.com/introducing-project-tinyminimicro-home-lab-revolution/).
 
-I created the case myself with simple arylglass :)
-
-Sources for good HW Ideas is of course the [TinyMiniMicro](https://www.servethehome.com/introducing-project-tinyminimicro-home-lab-revolution/)
-project from ServeTheHome. Or one of the many stores for older server center
-hardware like:
-
-
-I explicitly decided against using server center hardware because I wanted to
-have multiple actual nodes which have diffirent downtimes and outages. If I
-wouldn't use the cluster as homelab the obvious solution would be a few servers
-with virtualisation.
-
-
-Order on initialization:
-
-1. cluster itself
-2. argocd
-3. applicationset
-3. applicationset init
-    1. reference to self
-4. application set platform
-    1. metallb
-        * Add secret for memberlist
-    2. cert-manager
-        * Add token for digital ocean
-    3. traefik
-    4. longhorn
-        * longhorn disks mounted
-    5. 
+You can find more details [here](https://mikevader.github.io/k3s-cluster-infra-apps/).
 
 
 # copy volume to volume with rsync

docs/bare-metal.md

@@ -52,7 +52,6 @@ in the [MinIO Documentation][4].
 
 So your Opnsense Config looks something like this:
 
-|------------------------|----------------------------------|
 | Field                  | Value                            |
 |------------------------|----------------------------------|
 | Name                   | Upload Minio Certificate         |

docs/index.md

@@ -1,10 +1,13 @@
 # Raspberry Pi GitOps Stack
 
-This document describes my current setup of my Rasperry Pi k8s cluster. Although everything should be reflected in code, usually my brain discards stuff which works ... now. The not-working is a problem for future brain 😄
+This document describes my current setup of my Rasperry Pi k8s cluster. Although everything should be reflected in code,
+usually my brain discards stuff which works ... now. The not-working is a problem for future brain 😄
 
-So the text is mainly meant for me to keep track of how and why I did certain things. If somebody else finds value in it: great!
+So the text is mainly meant for me to keep track of how and why I did certain things. If somebody else finds value in
+it: great!
 
-Although the whole thing is a private project for educational purposes, I try to keep it as production ready as possible. Often the biggest learnings stem from corner cases. 
+Although the whole thing is a private project for educational purposes, I try to keep it as production ready as
+possible. Often the biggest learnings stem from corner cases. 
 That means, at least for me, to stay true to the following points:
 
 * Everything is automated, no manual kubectl commands
@@ -17,11 +20,13 @@ That means, at least for me, to stay true to the following points:
 
 ## Hardware
 
-I use the following harware setup for this:
+I use the following hardware setup for this:
 
 * 3 Raspberry PI 4s with 8GB Ram and Corsair GTX USB Stick as Disk
 * 4 Raspberry PI 4s with 8GB Ram, Corsair GTX USB Stick as Boot Disk and an
   external USB/NVME Drive (which has to be powered separatly)
+* Lenovo Thinkcentre M720q with 64GB Ram with Proxmox and large HDD
+* Lenovo Thinkcentre M75q with 64GB Ram with Proxmox and large HDD
 
 The first are used for the control plane, the other fours are used as worker
 nodes. Some of them are powered with PoE hats. The faster external drives are
@@ -33,6 +38,7 @@ Inspired from
 * https://github.com/onedr0p/home-ops
 * https://github.com/bjw-s/home-ops
 * https://github.com/dirtycajunrice/gitops
+* [TinyMiniMicro](https://www.servethehome.com/introducing-project-tinyminimicro-home-lab-revolution/)
 * 
 
 --8<-- "includes/abbreviations.md"