Commit Graph

23 Commits

Author SHA1 Message Date
Will Anderson 741191a7e6 Switch workers to custom WireGuard provider with correct endpoint IPs
gluetun's bundled protonvpn server list has stale IPs for US-TX#179
(37.19.200.26) and US-TX#220 (95.173.217.2). The WIREGUARD_ENDPOINT_IP
env var is a filter not an override, so there's no way to redirect
protonvpn provider to a new IP.

Switch to custom WireGuard provider with hardcoded endpoint IPs from
fresh ProtonVPN configs (95.173.217.29 / 146.70.58.130). Add
DNS_KEEP_NAMESERVER=on so gluetun leaves k8s DNS intact instead of
routing DNS through its own proxy (which breaks in-cluster).

Port forwarding is not available with custom provider; will restore
once gluetun releases an updated server list image.
2026-04-14 21:29:29 -05:00
Will Anderson 0688700ebc Fix gluetun endpoint env var: use WIREGUARD_ENDPOINT_IP, drop port
gluetun rejects VPN_ENDPOINT_PORT when SERVER_NAMES is used (server
selection mode), and warns that VPN_ENDPOINT_IP is deprecated in
favour of WIREGUARD_ENDPOINT_IP. Use only WIREGUARD_ENDPOINT_IP;
port 51820 is ProtonVPN's default and doesn't need to be set.
2026-04-14 21:25:55 -05:00
Will Anderson 87934e9284 Override stale gluetun endpoint IPs for ProtonVPN servers
ProtonVPN migrated US-TX#179 (37.19.200.26 → 95.173.217.29) and
US-TX#220 (95.173.217.2 → 146.70.58.130). gluetun's bundled server
list still has the old dead IPs. Override via VPN_ENDPOINT_IP and
VPN_ENDPOINT_PORT so gluetun uses the correct endpoints while keeping
the protonvpn provider (and port forwarding) intact.
2026-04-14 21:24:19 -05:00
Will Anderson 008df2b584 Fix server names: US-TX#179 for tx253, US-TX#220 for tx34 (gluetun protonvpn format) 2026-04-14 21:19:02 -05:00
Will Anderson a2239ab89e Switch back to protonvpn provider with US-TX#253 and US-TX#34 2026-04-14 21:17:20 -05:00
Will Anderson 88c4d795e7 Switch DNS to 8.8.8.8 — ProtonVPN internal DNS returning errors 2026-04-14 21:12:33 -05:00
Will Anderson 027667e7f7 Remove custom health target — use ProtonVPN internal DNS for resolution 2026-04-14 21:10:42 -05:00
Will Anderson e6d1350ca8 Use ProtonVPN internal DNS and direct IP healthcheck to diagnose VPN 2026-04-14 21:08:55 -05:00
Will Anderson 9778f79845 Configure per-worker VPN endpoints: tx253→US-TX#253, tx34→US-TX#34 2026-04-14 21:02:01 -05:00
Will Anderson fcff5f62e5 Switch worker base to custom WireGuard provider for US-IL#267 2026-04-14 20:31:03 -05:00
Will Anderson 7f7e2e26da Force coordinator rollout to pick up new image with downloadSpeedBps 2026-04-14 20:10:08 -05:00
Will Anderson 07f75c7dc8 Force UI pod rollout to pick up new nginx image 2026-04-14 19:57:32 -05:00
Will Anderson 87c4b63cca Route /api/ui through nginx to bypass Cloudflare Access; bump restartedAt
The /api/ui path is now routed to the fornax-ui nginx pod (which proxies
internally to the coordinator) rather than directly to the coordinator.
This fixes the browser fetch being blocked by Cloudflare Access.

Both coordinator and UI deployments get a restartedAt bump to pull the
new images after CI builds.
2026-04-14 19:44:23 -05:00
Will Anderson 3110903c81 Force rollout to pick up new images with real qBT wiring 2026-04-14 19:30:23 -05:00
Will Anderson 2a21c9d57e Fix fornax service port and add qBittorrent worker env vars
- fornax service: targetPort 8080→3000 (Express listens on 3000, not 8080)
  This was silently dropping all Radarr/Sonarr requests
- coordinator deployment: add QBT_WORKER_ADDRS, QBT_USER, QBT_PASS
  so /api/ui/state can query real worker qBittorrent instances
- remove Python coordinator ConfigMap and Deployment (superseded)
2026-04-14 19:17:00 -05:00
Will Anderson 788f103c0e Force UI rollout to pick up new image with CSS stylesheet 2026-04-14 19:02:48 -05:00
Will Anderson 7e2a7c7126 Force coordinator rollout to pick up new image with crash fix 2026-04-14 19:02:18 -05:00
Will Anderson 27d9d9c436 fornax: fix crash-looping coordinator, add UI deployment
- Fix liveness/readiness probe paths from /api/v2/app/version (qBittorrent)
  to /health and /health/ready (Fornax Express server). Pod was restarting
  every ~30s due to probe failures against wrong endpoint.
- Add fornax-ui deployment and service for React dashboard
  (image: fornax/ui:latest, nginx on port 80)
- Split ingress: /api and /health → coordinator:3000, / → ui:80
- Update kustomization to include UI resources
2026-04-14 08:45:21 -05:00
Will Anderson bdba692db2 Fornax: COORDINATOR_URL env, port-lease webhook, Grafana dashboard
- Worker deployment: add COORDINATOR_URL and WORKER_ID env vars to
  portforward-helper; webhook calls coordinator /api/v2/workers/:id/port-lease
  after each NAT-PMP renewal so coordinator tracks current forwarded port
- Worker overlays: patch WORKER_ID env var to actual worker ID (tx253/tx34)
- Grafana: fornax-grafana Argo CD app pointing to k8s/fornax/grafana/
  ConfigMap with grafana_dashboard=1 label for auto-discovery by sidecar;
  7 panels covering bandwidth, active torrents, worker health, request rate,
  and error rate
2026-04-14 05:30:01 +00:00
Will Anderson 4a0ebededf fix: revert to protonvpn provider, use server name from secret 2026-04-14 00:07:11 +00:00
Will Anderson 1cc783e704 fix: use custom gluetun provider with endpoint IP for ProtonVPN workers 2026-04-14 00:04:50 +00:00
Will Anderson eebd0226de fix: worker gluetun endpoint IP approach, add VPN key secrets 2026-04-14 00:01:43 +00:00
Will Anderson 180fb91c95 add fornax coordinator and worker k8s manifests 2026-04-13 23:57:22 +00:00