156 Commits

Include renames

Author	SHA1	Message	Date
Piotr Mlocek	53157595b5	fix(cluster): use iptables DNS proxy instead of host gateway for k3s DNS ... The previous approach wrote the host.docker.internal IP to the k3s resolv.conf, assuming it would serve DNS. On Docker Desktop, this IP is reachable but doesn't run a DNS server, causing CoreDNS to fail resolving external names and breaking the PKI job and Helm install. The new approach discovers Docker's embedded DNS listener ports from the DOCKER_OUTPUT iptables chain, then sets up DNAT rules to forward DNS traffic from k3s pods (via PREROUTING) to Docker's actual DNS resolver on 127.0.0.11. The container's eth0 IP is used as the nameserver in the k3s resolv.conf since it's routable from all pods.	2026-02-06 17:34:40 -08:00
Drew Newberry	00f432de8c	feat: add mtls support to plaform	2026-02-05 17:24:48 -08:00
John Myers	ff127c6ab2	chore(sandbox): add networking tools to sandbox image	2026-02-05 15:54:02 -08:00
Drew Newberry	e34444adf9	feat(sandbox): add ssh connect to sandbox + build agent harness	2026-02-05 07:58:20 -08:00
Drew Newberry	3c580b7cbf	test: add basic lint and test checks to ci	2026-02-05 00:14:13 -08:00
Drew Newberry	207ebe4a43	chore: cleanup docker/kube/helm infra	2026-02-04 23:00:17 -08:00