mats 64abb69c26 Route the DNS admin ingress to the separate console ...

The ingress still sent the UI and admin API to the resolver after the console split. Route both paths through the console so OIDC callbacks and Kubernetes edits reach their owner, while keeping DoH on the resolver.

Include the console resources in Kustomize so GitOps deploys its configuration, permissions, workload and Service alongside the resolver.

2026-10-16 11:45:29 +02:00

..

compose

rework

2026-10-16 11:13:13 +02:00

grafana

Add a Grafana dashboard for the resolver's metrics

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

k8s

Route the DNS admin ingress to the separate console

2026-10-16 11:45:29 +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

rework

2026-10-16 11:13:13 +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