Nik Afiq b17eceb950
Some checks failed
validate / lint (push) Failing after 8s
feat: serve PAC file routing nyaa.si via browser-vpn-proxy
Add a proxy-pac Argo CD Application: an nginx-unprivileged pod serving
http://proxy.home.arpa:8082/proxy.pac. The PAC sends nyaa.si and its
subdomains to the existing VLAN 50 SOCKS5 proxy (10.10.40.20:1080, which
resolves via Technitium's piracy-exempt group and egresses via PIA) with
no DIRECT fallback; everything else goes DIRECT. Intended for iOS, which
can't take a manual SOCKS proxy but honours SOCKS from a PAC.

Plain HTTP on a ServiceLB port because proxy.home.arpa already points at
10.10.40.20 in Technitium, while Traefik only answers on 10.10.40.53.
Port 8082 was checked free on all nodes; 8080 is taken on nik-debian.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-17 23:05:48 +09:00
..

Argo CD

Argo CD is the cluster reconciler for this repo. manifests/argocd/app-of-apps.yaml points Argo CD at argocd/apps, where each file defines one child Application.

Bootstrap

Install or upgrade Argo CD with the pinned chart values:

helm repo add argo https://argoproj.github.io/argo-helm
helm repo update
helm upgrade --install argocd argo/argo-cd \
  --namespace argocd --create-namespace \
  --version 9.4.15 \
  --values argocd/values/argocd.yaml

Then apply the app-of-apps:

kubectl apply -f manifests/argocd/app-of-apps.yaml

Argo CD is exposed at https://argocd.home.arpa by manifests/argocd/argocd.yaml.

Application Types

Type Examples Source
Helm chart plus values Traefik, cert-manager, Gitea, Pi-hole, monitoring, Loki, Tempo argocd/apps/*.yaml and values/*.yaml
Raw manifest directory Core, media, network secrets, home services, portfolio manifests/*
Argo CD self-management argocd-self, argocd-config argocd/values and manifests/argocd

Most Applications use automated sync with selfHeal: true and prune: false. Expect Argo CD to correct drift, but do not expect deleted Git resources to be pruned automatically.

Adding a Service

  1. Add raw manifests under manifests/<area> or Helm values under values/.
  2. Add an Application in argocd/apps/.
  3. Add any required DNS entries to both Pi-hole values files.
  4. Add certificates, secrets, and registry pull secrets if the service needs them.
  5. Commit and let the app-of-apps reconcile.

Use targetRevision: main for repo-managed services unless there is a specific reason to track HEAD.