matsandClaude Sonnet 5.5
1a536e7d0e
fancy-dns-console is a second binary holding the web UI, authentication and every edit. It writes ClientGroup, BlockList and DNSZone objects through the new kubeedit package and forwards all other /api routes to a running resolver with its own key, dropping the browser's credentials, so it can run in the cluster or on a workstation with a kubeconfig and nothing about the resolver's placement matters. The resolver never imports kubeedit and the console is not on the DNS path. kubeedit validates every spec with the runtime's own converters (kubesource.CheckGroup/CheckList/CheckZone) before writing, so the console cannot store an object the resolver would reject. Zone edits keep the file-based writer's behaviour: duplicate and below-a-delegation records are refused, a delegation in a new zone also gives the zone its servers, and a zone with no apex NS is never stored. Each object records the editing user in an annotation; updates retry on conflict. The resolver reports groups from ClientGroup objects as source "kubernetes" and counter-only rows (the "(default)" bucket, or a group removed since) as "history", and lists DNSZone zones as the editable ones. The console uses that to leave the YAML's groups alone and to drop history rows, which the UI would otherwise send back on save. Its GET /api/clients overlays the cluster's current objects on the resolver's list, because the resolver only sees an edit after its watch fires and a save made just after another would delete the first. An end-to-end test runs both halves against one fake apiserver: a group saved through the console refuses queries, a zone built record by record answers authoritatively, and a request with the resolver's own key is rejected by the console. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
18 lines
567 B
YAML
18 lines
567 B
YAML
# Console configuration for running fancy-dns-console on a workstation:
|
|
#
|
|
# export FANCYDNS_RUNTIME_KEY=... # a key the resolver's admin API accepts
|
|
# fancy-dns-console -config deploy/console.example.yaml \
|
|
# -runtime-url http://127.0.0.1:8080 -kube-namespace dns
|
|
#
|
|
# Credentials for the cluster come from -kubeconfig / $KUBECONFIG / ~/.kube/config.
|
|
blocklist: {enabled: false}
|
|
api:
|
|
enabled: true
|
|
listen: ["127.0.0.1:8081"]
|
|
base_path: /api
|
|
ui: true
|
|
auth:
|
|
mode: apikey
|
|
api_keys: ["${FANCYDNS_CONSOLE_KEY}"]
|
|
trust_loopback: false
|