docs: record production cutover freeze
This commit is contained in:
parent
8cc3241bc9
commit
f302d90638
3 changed files with 79 additions and 2 deletions
|
|
@ -184,7 +184,7 @@ evidence is in
|
|||
|
||||
```task
|
||||
id: CORE-WP-0011-T04
|
||||
status: todo
|
||||
status: progress
|
||||
priority: high
|
||||
```
|
||||
|
||||
|
|
@ -197,6 +197,24 @@ operator console, consumer smokes, and the first post-cutover write.
|
|||
Rollback must restore the prior traffic/tunnel target and database write path;
|
||||
the old runtime stays intact until stabilization closes.
|
||||
|
||||
Cutover progress 2026-08-21: explicit operator approval entered this gate.
|
||||
Helm revision 3 enabled the chart `0.3.1` Ingress on railiance01 while public
|
||||
DNS still targeted CoulombCore. The source application was reconnected with
|
||||
database-default read-only mode and continues serving health/readiness, so
|
||||
stale-DNS readers remain available and writers fail closed. A fresh frozen
|
||||
archive was captured, the backed-up target rehearsal rows were replaced, and
|
||||
the source `public` tables were mapped into target schema `core_hub`. All eight
|
||||
table counts and order-independent row-content digests match; Alembic
|
||||
`20260627_0002`, migration, the hardened verifier, direct target health/
|
||||
readiness, unauthenticated denial, and authenticated protected read pass.
|
||||
|
||||
The cutover is paused only for the IONOS `hub.coulomb.social` A-record change
|
||||
from `92.205.130.254` to `92.205.62.239`. Target cert-manager is waiting on
|
||||
that HTTP-01 propagation. Do not restore source writes until the DNS/TLS/public
|
||||
smoke decision either completes or rolls back. Current evidence and exact
|
||||
rollback state are in
|
||||
`docs/evidence/core-hub-railiance01-cutover-2026-08-21.md`.
|
||||
|
||||
## Stabilize and release CoulombCore dependencies
|
||||
|
||||
```task
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue