Fix services-check and update docs for Frigate migration to ringtail
Move mosquitto, ntfy, frigate, and frigate-notify pod checks from minikube-indri to k3s-ringtail context in services-check. Add nvidia-device-plugin check. Update documentation across 8 files to reflect the migration completed in PRs #216 and #217. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
parent
d5d32fe91f
commit
703cbc59e7
10 changed files with 62 additions and 29 deletions
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
title: Indri
|
||||
modified: 2026-02-09
|
||||
modified: 2026-02-19
|
||||
tags:
|
||||
- infrastructure
|
||||
- host
|
||||
|
|
@ -32,7 +32,7 @@ Primary BlumeOps server. Mac Mini M1 (2020).
|
|||
- [[caddy]] - Reverse proxy for `*.ops.eblu.me`
|
||||
|
||||
**Kubernetes (via minikube):**
|
||||
- [[apps|All k8s applications]]
|
||||
- [[apps|Most k8s applications]] (Frigate, Mosquitto, ntfy migrated to [[ringtail]] k3s)
|
||||
|
||||
**GUI Applications (manual start required):**
|
||||
- Docker Desktop - Container runtime for minikube
|
||||
|
|
|
|||
|
|
@ -63,7 +63,13 @@ Sync order: `1password-connect-ringtail` -> `external-secrets-crds-ringtail` ->
|
|||
|
||||
### Workloads
|
||||
|
||||
No k8s workloads currently deployed. K3s is available for future workloads (e.g. Frigate, running nix-built containers).
|
||||
| Workload | Namespace | Notes |
|
||||
|----------|-----------|-------|
|
||||
| [[frigate]] | `frigate` | NVR with GPU-accelerated detection (RTX 4080) |
|
||||
| [[frigate]]-notify | `frigate` | MQTT-to-ntfy alert bridge |
|
||||
| Mosquitto | `mqtt` | MQTT broker for Frigate events |
|
||||
| [[ntfy]] | `ntfy` | Push notification server |
|
||||
| nvidia-device-plugin | `nvidia-device-plugin` | Exposes GPU to pods via CDI + nvidia RuntimeClass |
|
||||
|
||||
### Manual Cluster Registration
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue