mats/fancy-dns
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

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

Browse Source 
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>
This commit is contained in:
matsandClaude Sonnet 5.5 committed 2026-10-16 10:34:31 +02:00
1 parent b513501773
commit 242bcd98d9
3 files changed
+19 -9
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

deploy/MIGRATION.md
+5 -4
View File
@@ -1,14 +1,15 @@
# Moving a ConfigMap deployment to cluster objects
Until now the console edited zones and address redirects by writing two
ConfigMaps (`fancy-dns-zones`, `fancy-dns-rpz`) through the resolver's service
account, and the domains page rewrote the config file. Those mechanisms are gone.
ConfigMap (`fancy-dns-zones`: zone files and the live address overrides) through
the resolver's service account (`fancy-dns-rpz` was only the seed the overrides
started from), and the domains page rewrote the config file. Those mechanisms are gone.
Everything the console edits is now an object:
| Was | Is |
|---|---|
| `zone--<apex>.zone` keys in the `fancy-dns-zones` ConfigMap | `DNSZone` |
| `address-overrides.rpz` in the `fancy-dns-rpz` ConfigMap | `AddressOverride` (one per name) |
| the `address-overrides.rpz` key in the **same** `fancy-dns-zones` ConfigMap | `AddressOverride` (one per name) |
| `blocklist.allow_entries` / `block_entries` | `DomainRule` (`inline-allow`, `inline-block`) |
| `blocklist.lists` with a URL | `BlockList` |
| `acl.groups` | `ClientGroup` |
@@ -29,7 +30,7 @@ kubectl apply -f deploy/k8s/console/console.yaml # the console, which writes t
## 2. Convert what you have
The command reads the two ConfigMaps from the cluster and, if you give it the
The command reads the ConfigMap from the cluster and, if you give it the
resolver's `config.yaml`, its URL lists, inline entries and ACL groups. By
default it only **prints** manifests.