Documentation
Grouped by the layer it belongs to. Nothing here is aspirational: each page describes what is running now.
Talos Linux
Nodes boot an immutable image and take their configuration from a machine config. No SSH, no package manager, no drift.
- Node images and upgradesWhat a node is made of, where the machine config lives, and how an upgrade reaches four machines without an operator watching.
Hardware
Two physical machines with consumer CPUs, one OCI VM, one libvirt VM. The specs decide what can be scheduled where.
- The four machinesCPU, memory, GPU and role for every node, from the capacity the API server reports.
GitOps
One repository, reconciled by Flux every few minutes. Renovate opens the pull requests, image automation rewrites the tag, and nothing else changes the cluster.
- How an application is deployedOne HelmRelease, a chart from helmforge, a floating image tag, and the pipeline that builds the image.
Network
Cilium is the CNI and the gateway. Gateway API resources define every hostname, external-dns writes the records, and two mesh networks cover the tailnet and the two sites.
- Gateway routes and DNSTwo Cilium Gateways, one wildcard certificate, and external-dns reading hostnames from HTTPRoute objects.
Storage
Ceph replicates each object across three nodes and hands out volumes; CloudNativePG runs PostgreSQL on those volumes with backups to object storage.
- Ceph and PostgreSQLStorage classes, replication factor, the CNPG cluster shape, and where the backups go.
Monitoring
Metrics, logs and traces with a short list of alerts. A signal earns its place only if it changes what I do at 3am.
- Monitoring stackWhat is collected, where it lands, which alerts exist, and how to read them.
AI stack
Work in progress. Sandboxed agent devboxes and MCP servers run today; model serving and GPU sharing are still moving.
- Agent sandboxes and MCPAgent devboxes as Kubernetes Sandboxes behind a gateway, and the MCP servers exposed to them. Partial by design.
Open source projects
Charts, build tools and conventions that came from other people's repositories, plus the projects contributed to from this one.
- kaniko and OSS Container Toolskaniko builds every image here without a Docker daemon. Google archived it in 2024; a group of maintainers took it over.
- helmforge chartsThe chart repository behind most applications here, including the generic chart that covers anything without an upstream chart.
- Home-ops communityThe homelab GitOps repositories whose layout this one follows, and where it deliberately differs.