Engineering notes
How each milestone was built and measured, the spikes that settled the risky questions, and the research behind the design. Point-in-time records, kept as they were written.
| Notes | What they hold |
|---|---|
| Milestone M1 | resolver, cache and upstreams, store drivers, zones, zonecache, controller |
| Milestone M2 | transfers, policy and blocking, list fetching, query log, hardening |
| Milestones M3 and M4 | API, authentication, CLI, dashboard, deployment assets, edge and VIP supervisors |
| Milestone M5 | end-to-end tests, the security review, the burn-down |
| Spikes | measurements taken before the milestones: kube store driver, blocking matcher, OIDC, QUIC transports, store validator |
| Research | studies of the projects kudurru learns from (Gravity, Technitium, Pi-hole, blocky and AdGuard Home, dnsdist and keepalived, and more) |
| Follow-ups | open work with its target milestone |
| Release checklist | the steps from a green main to a tag |
The research notes describe other projects for analysis only; several of them are GPL or EUPL, and nothing from them is ported into kudurru (licensing rule).