diff --git a/README.md b/README.md index f05998d..24e7912 100644 --- a/README.md +++ b/README.md @@ -72,7 +72,8 @@ flowchart TB Internet((Internet)) subgraph CF["Cloudflare"] - DNS["DNS + DDNS
*.tap-tap.win"] + DNS["Authoritative DNS + DDNS
*.tap-tap.win"] + PROXY["Reverse proxy
homeassistant / vaultwarden / nginx2"] end subgraph PVE["Proxmox VE host"] @@ -96,21 +97,26 @@ flowchart TB TW["Twingate connector"] - Internet --> DNS - DNS --> OPN + Internet -.->|"DNS lookup"| DNS + Internet ==>|"direct HTTP / HTTPS
all other services"| OPN + Internet -->|"proxied HTTP / HTTPS
homeassistant / vaultwarden / nginx2"| PROXY + PROXY -->|"HTTP / HTTPS"| OPN OPN -->|"HTTP / HTTPS"| SVC NAS -->|"NFS"| K3S Internet --> TW TW --> K3S ``` +Cloudflare is the authoritative DNS provider for every public hostname. It also reverse-proxies three specific services: Home Assistant, Vaultwarden and nginx2. All other public services are DNS-only: clients resolve the public A record and connect directly to the public IP, where OPNsense handles the inbound connection. + Traffic flow: 1. Public DNS records live in Cloudflare and are kept current by `cloudflare-ddns`. -2. OPNsense forwards HTTP/HTTPS to the K3s node at `192.168.1.119`. -3. Traefik routes requests to the correct Kubernetes Service based on the ingress host. -4. Twingate provides private, identity-aware access without exposing services publicly. -5. TrueNAS exports storage over NFS to the Kubernetes node for Nextcloud and media workloads. +2. For most services, the client connects directly to the public IP; OPNsense forwards HTTP/HTTPS to the K3s node at `192.168.1.119`. +3. Home Assistant, Vaultwarden and nginx2 are proxied through Cloudflare before reaching OPNsense. +4. Traefik routes requests to the correct Kubernetes Service based on the ingress host. +5. Twingate provides private, identity-aware access without exposing services publicly. +6. TrueNAS exports storage over NFS to the Kubernetes node for Nextcloud and media workloads. ## Infrastructure layers @@ -168,12 +174,13 @@ The live node reports `NixOS 26.05` and `K3s v1.35.4+k3s1` with embedded etcd. | LoadBalancer implementation | K3s ServiceLB (no MetalLB) | | Ingress address | `192.168.1.119` on ports 80/443 | | Traefik NodePorts | `30123` (HTTP), `32467` (HTTPS) | +| Cloudflare-proxied hostnames | `homeassistant.tap-tap.win`, `vaultwarden.tap-tap.win`, `nginx2.tap-tap.win` | **Load balancing:** MetalLB was previously used and has been removed. K3s built-in ServiceLB now implements `LoadBalancer` services by binding the node IP. MetalLB CRDs remain in the cluster as leftovers from the previous installation, but there is no MetalLB namespace, controller or address pool. -**DNS and exposure:** Cloudflare hosts public DNS, and `cloudflare-ddns` keeps A records pointed at the current public address. OPNsense forwards HTTP/HTTPS to Traefik. Twingate is used for zero-trust access to private services. A `cloudflared` manifest exists in the repository, but the connector is not deployed in the cluster. +**DNS and exposure:** Cloudflare is the authoritative DNS provider for all public names, and `cloudflare-ddns` keeps the A records pointed at the current public address. It also reverse-proxies three hostnames: Home Assistant, Vaultwarden and nginx2. All other services are DNS-only — clients resolve the public address and connect directly to the public IP, where OPNsense forwards HTTP/HTTPS to Traefik. Twingate is used for zero-trust access to private services. A `cloudflared` manifest exists in the repository, but the connector is not deployed in the cluster. -**TLS:** cert-manager issues certificates from Let's Encrypt using the Cloudflare DNS-01 challenge. Certificates are currently ready for ArgoCD, Gitea, Vault, Home Assistant, Jellyfin, Nextcloud, nginx2, OnlyOffice and Plex. The nginx demo and Vaultwarden ingresses are HTTP-only at the ingress level. +**TLS:** cert-manager issues certificates from Let's Encrypt using the Cloudflare DNS-01 challenge. Certificates are currently ready for ArgoCD, Gitea, Vault, Home Assistant, Jellyfin, Nextcloud, nginx2, OnlyOffice and Plex. The nginx demo (`nginx.tap-tap.win`) and Vaultwarden remain HTTP-only at the ingress level; Vaultwarden, Home Assistant and nginx2 are the hostnames proxied through Cloudflare. **Internal DNS:** Kubernetes uses CoreDNS for cluster service discovery. Public names resolve through Cloudflare, while TrueNAS provides persistent storage over NFS. @@ -290,15 +297,15 @@ Several directories are kept for reference or future use but are **not currently | OnlyOffice | `onlyoffice` | `onlyoffice.tap-tap.win` | OnlyOffice Document Server | | Plex | `plex` | `plex.tap-tap.win` | Media server using the Nextcloud media library | | Jellyfin | `jellyfin` | `jellyfin.tap-tap.win` | Media server using the Nextcloud media library | -| Vaultwarden | `vaultwarden` | `vaultwarden.tap-tap.win` | Password manager (HTTP ingress) | -| Home Assistant | `homeassistant` | `homeassistant.tap-tap.win` | Smart-home hub | +| Vaultwarden | `vaultwarden` | `vaultwarden.tap-tap.win` | Password manager (HTTP ingress; proxied through Cloudflare) | +| Home Assistant | `homeassistant` | `homeassistant.tap-tap.win` | Smart-home hub (proxied through Cloudflare) | | Mosquitto | `homeassistant` | internal | MQTT broker for Zigbee2MQTT and Home Assistant | | Zigbee2MQTT | `homeassistant` | NodePort `30080` / `30081` | Zigbee bridge with USB stick passthrough | | Matter Server | `homeassistant` | internal | Matter device integration | | OpenThread Border Router | `homeassistant` | host network | Thread border router with USB radio passthrough | | Twingate | `twingate` | — | Zero-trust connector | | Cloudflare DDNS | `cloudflare-ddns` | — | Updates public DNS records | -| nginx demo | `nginx` | `nginx.tap-tap.win`, `nginx2.tap-tap.win` | Simple ingress demo; `nginx.tap-tap.win` is HTTP-only, `nginx2` uses TLS | +| nginx demo | `nginx` | `nginx.tap-tap.win`, `nginx2.tap-tap.win` | Simple ingress demo; `nginx.tap-tap.win` is HTTP-only, while `nginx2` uses TLS and is proxied through Cloudflare | ArgoCD currently reports 14 application directories plus the root application, all `Synced` and `Healthy`. @@ -386,7 +393,7 @@ Observability is therefore a known gap and a roadmap item rather than a running - **No credentials in this README:** tokens, passwords, keys and private endpoints are intentionally excluded. - **Zero-trust remote access:** Twingate provides identity-aware access to private services without exposing them directly. - **Network separation:** Public ingress passes through OPNsense to Traefik; Twingate provides a separate identity-aware path for private access. The host firewall also permits cluster, Matter/Thread and NodePort ports, so isolation relies on OPNsense and the private LAN. -- **Minimal public surface:** services such as Vault, ArgoCD, Gitea and the media servers are protected by ingress and TLS; platform internals do not have public ingresses. +- **Minimal public surface:** services such as Vault, ArgoCD, Gitea and the media servers are protected by ingress and TLS; platform internals do not have public ingresses. Home Assistant, Vaultwarden and nginx2 additionally sit behind Cloudflare's reverse proxy. - **Data protection:** Borg repositories are encrypted, and the offsite copy is synchronised to Google Drive. ## Engineering highlights