Erich Blume 291fff345c Fix services-check and update docs for Frigate migration to ringtail (#218 )

## Summary
- Move mosquitto, ntfy, frigate, frigate-notify pod checks from `minikube-indri` to `k3s-ringtail` context in `services-check`
- Add `nvidia-device-plugin` pod check for ringtail k3s
- Rename "Kubernetes pods" section to "Indri minikube pods" for clarity
- Update 8 documentation files to reflect the migration completed in PRs #216/#217

## Files Changed
| File | Change |
|------|--------|
| `mise-tasks/services-check` | Move 4 pod checks to k3s-ringtail, add nvidia-device-plugin |
| `docs/reference/services/frigate.md` | Image→tensorrt, detector→ONNX/CUDA, shm→512Mi |
| `docs/reference/infrastructure/ringtail.md` | List actual k3s workloads |
| `docs/reference/infrastructure/indri.md` | Note frigate migration |
| `docs/explanation/architecture.md` | Add ringtail to diagram + compute layer |
| `docs/reference/kubernetes/cluster.md` | Note two clusters, add k3s section |
| `docs/reference/reference.md` | Update frigate/ntfy location |
| `docs/how-to/plans/completed/operationalize-reolink-camera.md` | Add post-completion migration note |
| `CLAUDE.md` | Add k3s-ringtail context guidance |

## Test plan
- [ ] `mise run services-check` — all checks pass
- [ ] Review each doc for accuracy against deployed state

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

Reviewed-on: https://forge.ops.eblu.me/eblume/blumeops/pulls/218

2026-02-19 14:38:21 -08:00

1.5 KiB

Raw Blame History

title

modified

Kubernetes Cluster

BlumeOps runs two Kubernetes clusters: a Minikube cluster on indri (most services) and a k3s cluster on ringtail (GPU workloads, MQTT, notifications). Both are managed by argocd on indri.

Cluster Specifications

Property	Value
Driver	docker
Container Runtime	docker
Kubernetes Version	v1.34.0
CPUs	6
Memory	11GB
Disk	200GB
API Server	https://k8s.tail8d86e.ts.net

Prerequisites: Docker Desktop with at least 12GB memory allocated.

Volume Mounting

Pods mount NFS directly from sifaka. Docker NATs outbound traffic through indri's LAN IP (192.168.1.50), allowing access to Sifaka's NFS exports.

Registry Mirror

Containerd uses zot as a pull-through cache at host.minikube.internal:5050.

Mirrors configured: registry.ops.eblu.me, docker.io, ghcr.io, quay.io

K3s on Ringtail

Single-node k3s cluster for workloads requiring amd64 or GPU access. See ringtail for cluster specs, workload list, and secrets management.

Property	Value
Context	`k3s-ringtail`
API Server	`https://ringtail.tail8d86e.ts.net:6443`
Workloads	Frigate (GPU), Mosquitto, ntfy, frigate-notify, nvidia-device-plugin

apps - ArgoCD applications
argocd - GitOps deployment
zot - Registry mirror

1.5 KiB Raw Blame History