Stand up railiance01 receiver without founder bao kv put
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s

Database leases come from ClusterSecretStore openbao-audit-core-database
(one extract, one lease). Senders are minted in-cluster. Secret mounts
use fsGroup 10001. Schema 0001-0004 applied after dropping the isolation
stub events table. /readyz reports custody_class=archive.
This commit is contained in:
tegwick 2026-08-13 10:27:13 +02:00
parent 3119ee33d6
commit 74575c4f32
10 changed files with 121 additions and 98 deletions

View file

@ -84,9 +84,10 @@ custody defect: stop and investigate.
## Sender credential rotation
The registry is OpenBao KV `platform/workloads/audit-core/senders`, field
`senders.json`, refreshed by ExternalSecret `audit-core-senders` every hour
and injected as `AUDIT_CORE_SENDERS`. Rotation is overlap-first:
First deploy mints the registry in-cluster as Secret `audit-core-senders`
(ops-mason plan `audit-core-openbao-runtime-custody`). The OpenBao path
`platform/workloads/audit-core/senders` is the later authority after a
wrap-migrate; do not `bao kv put` it by hand. Rotation is overlap-first:
1. Add the replacement token to the sender's `tokens` list. Both work.
2. Move the sender to the new token.