eblume/blumeops
1
1
Fork 0
Code Issues Pull requests Projects Releases 83 Packages Wiki Activity Actions

Review why-gitops doc: fix wiki-links, accuracy, add last-reviewed

Browse source 
- Fix misleading [[tailscale|Pulumi]] link → [[pulumi]]
- Simplify [[ansible|Ansible]] and [[argocd|ArgoCD]] to plain wiki-links
- Rename "Tailnet" layer to "Network" to reflect Pulumi's full scope (ACLs + DNS)
- Fix apt install → brew install (indri is macOS)
- Add [[pulumi]] to Related section
- Add last-reviewed frontmatter

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
Erich Blume 2026-02-13 16:47:28 -08:00
commit 40f220780d
2 changed files with 8 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

1
docs/changelog.d/review-why-gitops.doc.md Normal file
View file

@ -0,0 +1 @@
Review and fix why-gitops doc: correct wiki-links, fix apt->brew, broaden Pulumi scope, add last-reviewed.

12
docs/explanation/why-gitops.md
View file

@ -1,6 +1,7 @@
---
title: Why GitOps
modified: 2026-02-07
modified: 2026-02-13
last-reviewed: 2026-02-13
tags:
- explanation
- philosophy
@ -45,9 +46,9 @@ BlumeOps uses layered GitOps:
| Layer | Tool | What it manages |
|-------|------|-----------------|
| **Tailnet** | [[tailscale|Pulumi]] | ACLs, tags, DNS |
| **Host config** | [[ansible|Ansible]] | Services on [[indri]] |
| **Kubernetes** | [[argocd|ArgoCD]] | Containerized workloads |
| **Network** | [[pulumi]] | Tailscale ACLs, tags; Gandi DNS |
| **Host config** | [[ansible]] | Services on [[indri]] |
| **Kubernetes** | [[argocd]] | Containerized workloads |
Each layer has its own reconciliation loop:
- Pulumi applies on `mise run tailnet-up`
@ -59,7 +60,7 @@ Each layer has its own reconciliation loop:
GitOps isn't free:
- **Learning curve** - You need to understand Ansible, ArgoCD, Pulumi
- **Indirection** - Can't just `apt install` something; need to add it to config
- **Indirection** - Can't just `brew install` something; need to add it to config
- **Complexity** - More moving parts than a simple server
But for BlumeOps, the trade-off is worth it. The infrastructure is complex enough that managing it imperatively would be error-prone, and the GitOps approach enables effective AI-assisted operations.
@ -67,5 +68,6 @@ But for BlumeOps, the trade-off is worth it. The infrastructure is complex enoug
## Related
- [[architecture]] - How the pieces fit together
- [[pulumi]] - Network infrastructure as code
- [[argocd]] - Kubernetes GitOps
- [[ansible]] - Host configuration