.

doc/notes.txt

@@ -1,3 +1,9 @@
 Q: KubeConfig doesn't work, not valid for kube-vip IP, only for some "random" IPs in flannel network.
 A: This can happen when cluster is restarted, maybe if rancher pods are restarted, can be fixed with: kubectl annotate secrets -n cattle-system tls-rancher-internal listener.cattle.io/cn-<kube-vip>=<kube-vip>
 <kube-vip> = cluster IP address
+https://github.com/harvester/harvester/issues/1475
+
+Q: Need to boot with no nomodeset on harvester 0.3.0 nodes
+A: https://docs.harvesterhci.io/v0.3/troubleshooting/os/#how-to-change-the-default-grub-boot-menu-entry
+
+

doc/slackpost.md

@@ -15,7 +15,7 @@ I managed to complete two (and a half) of the requirements
 - [x] x86_64 and aarch64
 - [ ] Affordable
 
-It's more transportable than portable weighing in at TODO kg, and it's way more expensive to build than I would admit.
+It's more transportable than portable weighing in at just under 20kg, and it's way more expensive to build than I would admit.
 
 It consists of:
 - one [ASUS Minu PC PN50 Ryzen][pn50] as admin
@@ -43,12 +43,14 @@ The admin machine runs:
  - dnsmasq
  - cronyd
  - nginx
- - NFS
+ - NFS server
  - PXE, atftp
  - wireguard
+ - etc, etc..
 
 The admin machine is easily reinstalled and updated with script and by default I will be running harvester on the three remaining PN50s.
-However, they could be re-imaged with what ever I like because there's no "production" going on :)
+However, they could be re-imaged with what ever I like because there's no "production" going on.
+