matsandClaude Sonnet 5.5 242bcd98d9 migrate: read the live address overrides from the zones ConfigMap, not the seed ...

The old console kept the zone files and the live address-overrides.rpz in the
same fancy-dns-zones ConfigMap; fancy-dns-rpz was only the static seed the
overrides started from. Reading the live cluster showed the two had diverged
(6 entries against 5, the missing one being stackship.k6n.net), so the default
would have silently dropped a redirect. The default is now fancy-dns-zones, and
the test puts a different stale seed in fancy-dns-rpz so reading the wrong one
fails.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

2026-10-16 10:34:31 +02:00

..

grafana

Add a Grafana dashboard for the resolver's metrics

2026-10-16 09:57:38 +02:00

k8s

Deploy: read cluster objects, drop the zones and RPZ ConfigMaps

2026-10-16 10:19:47 +02:00

zones

Make the API response contract a test; fix what it found

2026-09-27 18:42:59 +00:00

config.example.yaml

Remove the ConfigMap, RPZ and managed-directory editors the cluster objects replace

2026-10-16 10:17:17 +02:00

console.example.yaml

Split the console from the resolver: fancy-dns-console writes the cluster

2026-10-16 08:43:41 +02:00

local.example.zone

half broken

2026-09-27 17:17:53 +00:00

MIGRATION.md

migrate: read the live address overrides from the zones ConfigMap, not the seed

2026-10-16 10:34:31 +02:00