docs(okf): switch reverse proxy to Caddy across bundle

own-proxy decision, terraform provisioner, system diagram, gateway SSE notes, server-budget comment and roadmap 0.4.0 now use Caddy with ACME-managed TLS instead of nginx plus certbot
This commit is contained in:
Noel Sabia committed 2026-10-15 14:44:49 +02:00
1 parent a1de7a5fae
commit f0a9d58cff
11 files changed
+37 -29

No files matched your search

+4 -4
View File
@@ -10,7 +10,7 @@ commands.
|---|---|---|
| Server, packages, swap, k3s install | Terraform (SSH provisioner, cloud-init or shell) | `fallocate`, `mkswap`, k3s service with trimmed config |
| DNS records | Terraform provider for the DNS zone | A/AAAA record for the apex domain |
| Reverse proxy | Terraform-installed nginx + certbot, config templated | server block to the gateway |
| Reverse proxy | Terraform-managed Caddy, Caddyfile templated | reverse_proxy block to the gateway |
| Workloads inside k3s | kustomize, applied by CI or hand | Namespace `cv`, Deployments, Jobs, Services, quota |
Terraform does not manage anything inside the cluster. Kubernetes already
@@ -20,7 +20,7 @@ describes its own state; Terraform and kubectl would fight over it.
```
terraform/
main.tf server: packages, swap, k3s, nginx, certbot
main.tf server: packages, swap, k3s, Caddy
dns.tf A record for the apex domain
variables.tf server IP, SSH key, domain
outputs.tf server IP, proxy URL
@@ -31,8 +31,8 @@ Plan output for one run:
```
+ swapfile 2 GB
+ k3s service (traefik, servicelb disabled)
+ nginx server block -> http://127.0.0.1:8080 (gateway NodePort)
+ certbot certificate for noelsabia.dev
+ Caddy reverse_proxy block -> http://127.0.0.1:8080 (gateway NodePort)
+ certificate for noelsabia.dev
```
## Why