An AEvolution-only Prometheus 3.13.3 and Alertmanager 0.34.1, pinned by digest and delivered by Argo (ADR-0072), scrape each region's operations Service through static targets (no API access, no RBAC); the region namespaces admit port 9100 from Prometheus only. Sixteen alert rules cover authority, lease, commits, backlog and object capacity and are proven by promtool injection tests in CI with tools copied from the same pinned images. Two new gauges expose object volume free space and the reserve. Alerts route to a null receiver until a destination is chosen; no broker is adopted and the database outbox stays. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
3.3 KiB
3.3 KiB
Backlog
These items are deferred on purpose, or they await a maintainer decision. They are not scheduled roadmap gates. When a roadmap gate depends on an item, the gate names it. Remove an item only when it is done, and record where it was done.
| Item | Raised | Why deferred | Needed before |
|---|---|---|---|
World0 break-glass membership. Decide who may act as aevolution:world0-break-glass, and how that group is granted: for example a short-lived client certificate with that organization, or an OIDC group. Decide also how its use is approved and recorded. The admission policy already enforces the group (ADR-0069). |
M8.2, 2026-09-29 | Maintainer: figure out later | Any intentional deletion of World0 data or identity; M8.8 World0 launch |
Backup destination for dev/stage stores. There are no backups yet (maintainer, 2026-09-29). The plan is to build backup tooling for the AEvolution PostgreSQL VM and each aevolution-objects volume up to a pluggable destination, then add the destination. It must be off the host for anything beyond disposable environments. |
M8.3, 2026-09-29 | The maintainer will supply a destination later | M8.7 backup and restore; any World0 data |
| Secret manager for Argo-delivered configuration. Secrets are still created by hand (ADR-0069 amendment). Choose how they reach the cluster through Git or Argo: for example Vault with the Agent Injector (as in the maintainer's other environment), or sealed or external secrets. Until then, rotate by hand. | M8.3, 2026-09-29 | The maintainer wants everything through Argo; a secret manager is not chosen | Stage and World0 credentials; M8.4 |
Store Job values. Supply the published registry digests for aevolution-postgres-tools and aevolution-server (from each CI Publish step's Digest: line), and the NOLOGIN runtime group role for dev (aevolution) and for stage (aevolution_stage). Then include stores/<env> in each environment's path. |
M8.3, 2026-09-29 | Values pending | M8.3 in-cluster evidence |
| Alert destination. Alertmanager routes every alert to a null receiver (ADR-0072). Choose where alerts go (Discord, email, a webhook), and optionally a heartbeat receiver for the always-firing Watchdog. Receiver credentials go in a Secret. | M8.5, 2026-09-30 | The maintainer will decide later | Any claim that alerts reach a person; M8.6 alert evidence; World0 |
Kubelet log rotation check. Confirm the RKE2 nodes' container-log-max-size and container-log-max-files (default 10Mi × 5), which bound region host logs (ADR-0072). |
M8.5, 2026-09-30 | Needs node access | M8.6 |
Storage after the RAID/disk rework. Re-run deploy/kubernetes/inventory/disk-probe-local-path.yaml (or a new class), and update INVENTORY.md. |
M8.1, 2026-09-29 | Maintainer is reorganizing disks | M8.3's final storage decision |
Accepted risks (maintainer decisions)
| Decision | Date | Consequence | Mitigation in place |
|---|---|---|---|
Argo CD's default AppProject stays unrestricted |
2026-09-29 | Applications in default (other projects, two with automated prune) can create objects in any namespace, including AEvolution's. |
The World0 admission policy denies every deletion of World0 data, identity and delivery objects, whatever the project (ADR-0069). The AEvolution projects themselves are scoped. |