GitOps repository for personal infrastructure management
  • Nix 32.5%
  • Jinja 21.5%
  • Python 17.9%
  • Shell 11.8%
  • Go 8.1%
  • Other 8.2%
Find a file
Erich Blume be30668eef Automate Prowler MANUAL finding verification (#335)
## Summary
- Adds automated node-level verification to `review-compliance-reports`: kubelet file perms/ownership, kubelet config args, etcd CA separation, RBAC cluster-admin bindings
- Mutes the 14 MANUAL Prowler findings via new `manual-node-checks.yaml` mutelist file
- New `node-config-automated-verification` compensating control documents the approach
- Script fails loudly (red FAIL + verdict panel) if any check deviates from expected values

## Test plan
- [x] `mise run review-compliance-reports` — all 12 node checks PASS
- [x] Injected bad expected value (perms 400 vs actual 600) — FAIL rendered correctly
- [x] Fixed colon-in-binding-name bug (kubeadm:cluster-admins) with tab-separated jsonpath
- [ ] After merge: sync prowler mutelist ConfigMap and verify next scan shows 0 MANUAL findings

## Note
Prowler coverage is minikube-indri only — ringtail/k3s is a known gap tracked separately.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Reviewed-on: #335
2026-04-14 13:00:44 -07:00
.claude
.forgejo/workflows Route Dagger build telemetry to Tempo 2026-04-13 08:27:12 -07:00
.github
ansible Add paperless DB to borgmatic backups 2026-04-13 17:58:06 -07:00
argocd Automate Prowler MANUAL finding verification (#335) 2026-04-14 13:00:44 -07:00
containers Build forgejo-runner container locally (#334) 2026-04-14 11:06:36 -07:00
docs Automate Prowler MANUAL finding verification (#335) 2026-04-14 13:00:44 -07:00
fly
mise-tasks Automate Prowler MANUAL finding verification (#335) 2026-04-14 13:00:44 -07:00
nixos/ringtail Update ringtail flake inputs 2026-04-11 21:14:46 -07:00
pulumi
src/blumeops Route Dagger build telemetry to Tempo 2026-04-13 08:27:12 -07:00
utils/qart
.ansible-lint
.gitattributes Native Dagger container builds + Navidrome v0.61.1 (#330) 2026-04-11 17:11:56 -07:00
.gitignore Native Dagger container builds + Navidrome v0.61.1 (#330) 2026-04-11 17:11:56 -07:00
.yamllint.yaml
Brewfile
CHANGELOG.md Update docs release to v1.15.6 2026-04-14 11:46:42 -07:00
CLAUDE.md Document DR rebuild procedure and update restart-indri 2026-04-13 18:07:54 -07:00
compensating-controls.yaml Automate Prowler MANUAL finding verification (#335) 2026-04-14 13:00:44 -07:00
dagger.json Native Dagger container builds + Navidrome v0.61.1 (#330) 2026-04-11 17:11:56 -07:00
LICENSE
mise.toml Hints about service version tracking 2026-04-13 08:40:49 -07:00
prek.toml Miniflux 2.2.19 + container.py migration + ty typechecker (#331) 2026-04-12 08:54:32 -07:00
pyproject.toml Miniflux 2.2.19 + container.py migration + ty typechecker (#331) 2026-04-12 08:54:32 -07:00
README.md
service-versions.yaml Migrate teslamate to native Dagger container.py (#333) 2026-04-14 07:20:52 -07:00
towncrier.toml
uv.lock Add uv.lock for version pinning of dagger pipeline 2026-04-13 08:35:01 -07:00

blumeops

aka "Blue Mops"

Tools and configuration for Erich Blume's personal infrastructure, orchestrated across a Tailscale tailnet.

This is a homelab, but it's also a testing ground for AI-assisted infrastructure development. Much of this codebase was co-authored with Claude Code, and the repo places heavy emphasis on documentation, process, and change classification to make that collaboration work well. I don't know entirely how I feel about LLMs in our current era (there are real concerns about how training data is sourced and energy subsidy) but it felt important to learn how to work with these tools.

The full documentation is published at docs.eblu.me and lives in the docs/ directory, structured around the Diataxis framework and designed to be compatible with Obsidian/Obsidian.nvim.

What runs here

Services are a mix of Kubernetes pods (managed by ArgoCD), macOS LaunchAgent services (managed by Ansible), and NixOS systemd services (managed by Nix flakes), all connected via Tailscale:

  • Indri (Mac Mini M1) - primary server. Most services run in Minikube via ArgoCD; Forgejo, Caddy, and others run natively as LaunchAgent services via Ansible.
  • Ringtail (NixOS desktop, RTX 4080) - GPU workloads (Frigate NVR, Authentik SSO) on k3s, plus NixOS systemd services.
  • Sifaka (Synology NAS) - backup target and bulk storage.

Notable services include Grafana/Prometheus/Loki observability, Immich photos, Jellyfin media, Forgejo git forge, a Zot container registry, and more. Public access is routed through a Fly.io proxy; everything else is tailnet-only.

Project structure

ansible/            Ansible playbooks and roles (indri, sifaka)
argocd/apps/        ArgoCD Application definitions
argocd/manifests/   Kubernetes manifests per service
containers/         Custom container builds (Dockerfile + Nix)
docs/               Diataxis documentation (published at docs.eblu.me)
fly/                Fly.io public proxy configuration
mise-tasks/         Operational scripts run via mise
nixos/              NixOS configuration for ringtail
pulumi/             Pulumi IaC (Tailscale ACLs, Gandi DNS)
.dagger/            Dagger CI pipelines
.forgejo/           Forgejo Actions CI/CD workflows

Getting started

You'll need Homebrew and mise:

brew bundle                    # install CLI tools (argocd, tea, flyctl, etc.)
mise install                   # install managed toolchains (ansible, pulumi, dagger, etc.)
prek install                    # set up git hooks

Git hooks (via prek) enforce secret scanning (TruffleHog), linting, formatting, and custom checks like doc link validation and the Mikado branch invariant. They run automatically on git commit.

Operational tasks are driven through mise. Run mise tasks to see what's available. Key examples:

mise run provision-indri       # deploy to indri via Ansible
mise run services-check        # verify service health
mise run container-list        # list tracked container images

AI-assisted development

This repo is designed to be worked on by both humans and AI agents. The CLAUDE.md file provides instructions for Claude Code, and the docs/tutorials/ai-assistance-guide.md explains the full workflow.

Changes are classified before starting work:

  • C0 - quick fixes, committed directly to main
  • C1 - feature branch + PR, documentation written before code
  • C2 - multi-phase work using the Mikado method for dependency tracking

See the agent change process for details.

License

GPLv3