chore: document T14s GitOps success and osTicket reset
This commit is contained in:
parent
a14accd065
commit
25e1cb38a9
1 changed files with 17 additions and 1 deletions
|
|
@ -7,7 +7,23 @@ metadata:
|
|||
originSessionId: 33992890-3940-4d4a-a94a-22b5621e9c1a
|
||||
---
|
||||
|
||||
## STATUS: MIGRATION + CLOUD FAILOVER COMPLETE (2026-06-10)
|
||||
## T14s GitOps Automation SUCCESS (2026-06-15)
|
||||
|
||||
The cluster configuration originally for "assassin" (T14) has been moved to the
|
||||
**T14s**. The machine is now fully bootstrapped with FluxCD GitOps.
|
||||
|
||||
- **Cluster Hostname:** monk (T14s)
|
||||
- **GitOps Repo:** `kitestacks-homelab` (main branch)
|
||||
- **Path:** `clusters/T14s`
|
||||
- **Automation:** FluxCD is now managing the `kavita` namespace.
|
||||
- **Kavita Manifests:**
|
||||
- Deployment, Service, PVC (2Gi local-path), and Namespace.
|
||||
- Successfully synced and running (verified 2026-06-15).
|
||||
- **Credentials:** Authentik password for `kenpat7177` reset to `KiteStacks2026!`.
|
||||
- **osTicket:** Services started, DB unified on kscloud1, and verified
|
||||
accessible via Authentik LDAP.
|
||||
|
||||
The GitOps workflow is now the authoritative way to manage Kubernetes apps on the T14s.
|
||||
|
||||
monk is the live production host. assassin (T14) is OFF. kscloud1 (Hetzner VPS,
|
||||
5.78.233.28) is now a THIRD active Cloudflare Tunnel connector and runs a FULL
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue