Rancher — role and timing (k3s homelab / farm platform)¶
Purpose¶
Define what Rancher adds to a k3s + Pi stack, when to install it, and what to avoid prematurely—grounded in captures, not a full Rancher install guide.
Doctrine package: Platform doctrine package — homelab / farm edge (chapter Rancher).
Sources: rancher-k3s product page (positioning), Pi + Longhorn homelab (Helm / Apps install narrative). Official install (external): Rancher on Kubernetes—verify version pin at deploy time.
What Rancher is (here)¶
- Multi-cluster / CD story with K3s at edge per product page (
capture). - In-cluster management UI + Helm app catalog for Longhorn (
homelab narrative).
What Rancher is not¶
- Not required for k3s API or kubectl workflows.
- Not a substitute for backup / DR testing (
Kubernetes platform backup / DR).
Timing recommendation (this wiki)¶
| Phase | Rancher |
|---|---|
| 0–1 pilot | Defer unless you need multi-cluster CD or a UI for operators who will not use kubectl |
| After stable k3s + Longhorn + one stateful app (e.g. farmOS trial) | Optional Helm install; harden ingress + auth per Rancher docs |
| Production | Treat Rancher as a critical workload: backup PVC/values, patch cadence, RBAC |