Time guide
Basic controller health check: approximately 5 to 10 minutes Source or reconciliation investigation: approximately 15 to 30 minutes Purpose # Use this entry when Flux resources are not reconciling, a source is stale, or one of the controllers appears unhealthy.
Time guide
Initial cluster triage: approximately 10 to 20 minutes Standard health review: approximately 30 minutes Full platform, storage and host review: approximately 30 to 60 minutes The actual duration depends on cluster size, access availability and whether any checks identify faults that need further investigation.
A tunnel-based public access design with two cloudflared replicas, selective edge controls and CrowdSec-informed enforcement.
A website-like internal operations portal that unifies live telemetry from eleven validated APIs without replacing authoritative tools.
A layered recovery system combining Longhorn replication, daily snapshots, weekly QNAP backups and Veeam tape archival.
Encryption and recovery controls for 31 Git-managed Kubernetes Secret manifests using SOPS, age and Flux.
A declarative delivery system using Flux, Kustomize, Helm, image automation and encrypted Git-managed secrets.
A power-efficient, highly available four-node Kubernetes platform built with Raspberry Pi 5 hardware, k3s, Longhorn and GitOps.