feat: add content

astro.config.mjs

@@ -35,13 +35,17 @@ export default defineConfig({
         starlightThemeRapide()
       ],
       sidebar: [
+        {
+          label: "Reference",
+          autogenerate: { directory: "reference" },
+        },
         {
           label: "Guides",
           autogenerate: { directory: "guides" },
         },
         {
-          label: "Reference",
+          label: "Applications",
-          autogenerate: { directory: "reference" },
+          autogenerate: { directory: "applications" },
         },
       ],
     }),

src/content/docs/guides/example.md

@@ -1,11 +0,0 @@
----
-title: Example Guide
-description: A guide in my new Starlight docs site.
----
-
-Guides lead a user through a specific task they want to accomplish, often with a sequence of steps.
-Writing a good guide requires thinking about what your users are trying to do.
-
-## Further reading
-
-- Read [about how-to guides](https://diataxis.fr/how-to-guides/) in the Diátaxis framework

src/content/docs/guides/talos-upgrade.md

@@ -0,0 +1,75 @@
+---
+title: Talos Upgrade
+description: Steps followed for the v1.12.0 upgrade process
+---
+
+The upgrade to this version was more extension as there have been migrations to using configuration documents. This required rewriting the configuration document to a series of patches and provide a deterministic generation command for the different host types. In addition there was also a change to storage layout to separate ceph, local-path, and ephemeral storage on the NUC hosts.
+
+## Preparation
+
+The NUC hosts are to be wiped since because of the storage reconfiguration. For the RPIs only the first command with proper image was needed. The new configuration format could be applied later. Both the node and the disks have to be removed.
+
+The following command is used to upgrade the image. This was first to ensure the boot after wipe would still be v1.12.0 to use the updated configuration documents.
+```bash
+talosctl upgrade --nodes 10.232.1.23 --image factory.talos.dev/metal-installer/495176274ce8f9e87ed052dbc285c67b2a0ed7c5a6212f5c4d086e1a9a1cf614:v1.12.0
+```
+
+Wipe command.
+```bash
+talosctl reset --system-labels-to-wipe EPHEMERAL,STATE --reboot -n 10.232.1.23
+```
+
+## Remove old references
+
+Remove the node from the cluster.
+```bash
+kubectl delete node talos-9vs-6hh
+```
+
+Exec into the rook-ceph-tools container in order to remove the disk from the cluster.
+```bash
+kubectl -n rook-ceph exec -it $(kubectl -n rook-ceph get pod -l "app=rook-ceph-tools" -o jsonpath='{.items\[\*].metadata.name}') -- bash
+```
+
+Inside the rook-ceph-tools container remove the OSD/disk and the node:
+```bash
+ceph osd tree
+```
+```bash
+ceph osd out 0
+```
+```bash
+ceph osd purge 0 --yes-i-really-mean-it
+```
+```bash
+ceph osd crush remove talos-9vs-6hh
+```
+
+# Apply new configuration
+
+The wiped node should now be in maintenance mode and ready to be configured. Use the generate command in the README of the talos-config repo to make the configuration to be supplied.
+```bash
+talosctl apply-config -f generated/worker-nuc.yaml -n 10.232.1.23 --insecure
+```
+
+Add the required labels if Talos does not add them:
+```yaml
+node-role.kubernetes.io/bgp: '65020'
+node-role.kubernetes.io/local-storage-node: local-storage-node
+node-role.kubernetes.io/rook-osd-node: rook-osd-node
+```
+
+## Verification
+
+Verify the disks have been created:
+```bash
+talosctl get disks -n 10.232.1.23
+```
+ 
+ Verify the mount paths and volumes are created:
+```bash
+talosctl -n 10.232.1.23 ls /var/mnt
+```
+```bash
+talosctl -n 10.232.1.23 get volumestatuses
+```

src/content/docs/index.mdx

@@ -8,7 +8,7 @@ hero:
     file: ../../assets/autumn_mountain.png
   actions:
     - text: Introduction
-      link: /reference/example/
+      link: /reference/introduction/
       icon: right-arrow
 ---
 
@@ -17,9 +17,6 @@ import { Card, CardGrid, LinkCard } from '@astrojs/starlight/components';
 ## Hightlights
 
 <CardGrid stagger>
-  <Card title="Add new content" icon="add-document">
-    Add Markdown or MDX files to `src/content/docs` to create new pages.
-  </Card>
   <LinkCard
     title="Homepage"
     description="Visit my homepage to see what I'm up to and learn more about me."

src/content/docs/reference/example.md

@@ -1,11 +0,0 @@
----
-title: Example Reference
-description: A reference page in my new Starlight docs site.
----
-
-Reference pages are ideal for outlining how things work in terse and clear terms.
-Less concerned with telling a story or addressing a specific use case, they should give a comprehensive outline of what you're documenting.
-
-## Further reading
-
-- Read [about reference](https://diataxis.fr/reference/) in the Diátaxis framework

src/content/docs/reference/introduction.md

@@ -0,0 +1,16 @@
+---
+title: Introduction
+description: Overiew of the homelab
+sidebar:
+  order: 1
+---
+
+Overview of the homelab.
+
+# Hardware
+
+Currently using a mix of RPIs, Intel based NUCs, Synology NAS, and Ubiquity networking.
+
+# Software
+
+Kubernetes for the main cluster. Docker managed by Komodo for the single hosts.