Advance OpenBao migration to consumer waves

This commit is contained in:
codex 2026-08-03 21:30:17 +02:00
parent 50a0a2ab50
commit cb428442eb
3 changed files with 33 additions and 4 deletions

View file

@ -123,7 +123,7 @@ output was non-empty. Machine-readable evidence is in
```task
id: RAILIANCE-WP-0020-T04
status: wait
status: done
priority: high
state_hub_task_id: "d04d7fdd-bd00-407a-8954-101b680ed327"
```
@ -136,11 +136,22 @@ change public DNS or consumers yet.
Done when target semantic probes match the source and repeated restart/unseal
tests pass through a private endpoint.
Completed 2026-08-03. A final source snapshot was encrypted and uploaded
offsite (plaintext SHA-256
`ac5e27536c01c3a019c3dde1069866569112c76d8ab42ec2bdb45724cc9b13f8`,
encrypted SHA-256
`22003d8fcb12ef17d6edafad9358ed2b0e538b21a8daee86445d9b85482f9161`).
The still-empty railiance01 target was restored privately, temporary init
material and plaintext staging were removed, and two attended target
restart/unseal cycles passed. The target is active on OpenBao 2.5.4 with the
source cluster ID and a non-empty persistent audit file. CoulombCore remains
live and no public DNS changed.
## T05 - Migrate consumers to local workload identity
```task
id: RAILIANCE-WP-0020-T05
status: wait
status: progress
priority: high
state_hub_task_id: "f0a82e4e-8074-4a22-b1e9-f01ec0ff76a1"
```
@ -154,6 +165,11 @@ rollout, and reversal before continuing.
Done when all railiance01 consumers use the local private service and no
runtime dependency requires the CoulombCore API.
2026-08-03: Wave 1 (`reuse`) moved to
`http://openbao.openbao.svc:8200`. The ClusterSecretStore remained Valid, a
forced ExternalSecret refresh completed as SecretSynced/Ready, and the
declarative owner change was committed in `railiance-platform@33b36e8`.
## T06 - Cut over public OpenBao DNS and operator access
```task