Some checks failed
validate / lint (push) Failing after 8s
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>
61 lines
2.7 KiB
Markdown
61 lines
2.7 KiB
Markdown
# Kubernetes Manifests
|
|
|
|
This directory contains raw Kubernetes resources grouped by service area. Most
|
|
subdirectories are consumed by Argo CD Applications in `argocd/apps`.
|
|
|
|
## Directories
|
|
|
|
| Directory | Contents |
|
|
| --- | --- |
|
|
| `argocd/` | App-of-apps, Argo CD ingress, Argo CD OIDC sealed secret |
|
|
| `authentik/` | Authentik ingress, public ingress, proxy outpost, middleware, secret scripts |
|
|
| `cert-manager/` | Internal and Let's Encrypt ClusterIssuers, Porkbun secret script |
|
|
| `core/` | Dashy, Glances, CoreDNS custom config, CA installer |
|
|
| `gitea/` | Gitea storage, backup, public ingress, runner and OIDC/admin secrets |
|
|
| `home-services/` | HA gateway, AI gateway, Discord bot, service TLS, registry secret |
|
|
| `homeassistant/` | Home Assistant external service and ingress |
|
|
| `me-nik4nao-com/` | me.nik4nao.com deployment, ingress, registry pull secret |
|
|
| `media/` | Jellyfin, qBittorrent, JDownloader ([sending links](media/jdownloader.md)) |
|
|
| `monitoring/` | Monitoring PVs, Grafana datasource, Grafana/Auth OIDC secrets |
|
|
| `multus/` | Multus CNI, VLAN 50 NetworkAttachmentDefinition, canary, browser-vpn-proxy SOCKS5 proxy ([details](multus/README.md)) — manual-sync Application, see `argocd/apps/multus.yaml` |
|
|
| `network/` | Pi-hole secrets, DDNS, Traefik dashboard, external host ingresses |
|
|
| `portfolio/` | Portfolio deployment, ingress, registry pull secret |
|
|
| `proxy-pac/` | PAC file at `http://proxy.home.arpa:8082/proxy.pac` routing nyaa.si via browser-vpn-proxy (for iOS) |
|
|
|
|
## Secrets
|
|
|
|
There are two patterns:
|
|
|
|
- `*-sealed.yaml` files are safe to commit and are reconciled by Sealed Secrets.
|
|
- `*.sh` scripts create runtime Secrets from `.env` directly in the cluster.
|
|
|
|
Use `.env.example` as the template for local secret names. `kubeseal` must point
|
|
at the in-cluster controller named `sealed-secrets-controller` in `kube-system`.
|
|
|
|
Regenerate committed sealed secrets with the matching script, then commit the
|
|
resulting YAML. Runtime secret scripts should be run against the target cluster
|
|
and should not produce committed plaintext.
|
|
|
|
## Certificates
|
|
|
|
Internal services generally use `internal-ca-issuer` and `home.arpa` hostnames.
|
|
Public services use Let's Encrypt issuers and `nik4nao.com` hostnames.
|
|
|
|
The CA installer lives in `core/ca-installer`. Its `ca-sync` CronJob keeps the
|
|
served `ca.crt` and Apple mobileconfig in sync with the cert-manager CA secret.
|
|
|
|
## DNS
|
|
|
|
Internal DNS records are configured in `values/pihole.yaml` and
|
|
`values/pihole-debian.yaml`. Add a new hostname to both files when adding a
|
|
`home.arpa` service.
|
|
|
|
## Dashy
|
|
|
|
`core/dashy.yaml` defines the deployment and a placeholder ConfigMap. The real
|
|
dashboard config comes from `config/dashy/conf.yaml`:
|
|
|
|
```bash
|
|
bash manifests/core/apply-dashy-config.sh
|
|
```
|