Architecture decisions¶
| ADR | Decision | Status |
|---|---|---|
| 0001 | Record architecture decisions | Accepted |
| 0002 | Three repositories | Accepted |
| 0003 | GitOps-only, typed remediation | Accepted |
| 0004 | GitHub and Flux first, behind interfaces | Accepted |
| 0005 | Go, Kubebuilder, one module with two binaries | Accepted |
| 0006 | GitHub App with its private key in Key Vault | Accepted |
| 0007 | Incident state in CRDs for the MVP | Accepted |
| 0008 | A disposable Azure lab in its own subscription | Accepted |
| 0009 | API group and docs domain | Accepted |
| 0010 | Docs site built with Zensical on GitHub Pages | Accepted |
| 0011 | Policy as a cluster-scoped CRD | Accepted |
| 0012 | Mapping an object to its source in Git | Accepted |
| 0013 | An interface and adapters for every external system | Accepted |
| 0014 | Notifications through GitHub issues first | Accepted |
| 0015 | Analysis records are kept and outlive the lab | Accepted |
| 0016 | Lab region Sweden Central | Accepted |
| 0017 | Prometheus in the lab | Accepted |
| 0018 | Three axes of pluggability | Accepted |
| 0019 | Packaging extensions: compiled in now, signed OCI packs later | Proposed |
New ADR: copy the template, take the next number, add a row here.