coulomb/net-kingdom
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Verify railiance01 identity dependencies
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details

Browse source
This commit is contained in:
tegwick 2026-07-28 12:59:12 +02:00
parent d674d7f33a
commit 43045cbaf5
4 changed files with 170 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

11
workplans/NK-WP-0022-railiance01-identity-cutover-and-coulombcore-retirement.md
View file

@ -141,7 +141,7 @@ CoulombCore writers remain frozen against divergence.
```task
id: NK-WP-0022-T04
status: wait
status: done
priority: high
state_hub_task_id: "33591ee3-586e-4ac6-82e6-0ab4642cea5e"
```
@ -155,6 +155,15 @@ points back to CoulombCore.
Done when an automated dependency graph and negative search prove there are
no hidden CoulombCore runtime dependencies.
2026-07-28: added
`sso-mfa/k8s/verify-identity-cutover-dependencies.sh`. Its live railiance01
run found no CoulombCore IP/host or public cross-cluster endpoint in decoded
identity Secrets, ConfigMaps, Deployments, or StatefulSets. It verified
cluster-local KeyCape and privacyIDEA dependencies, retained user-engine and
rapp-qonto clients, and Ready deployments. KeyCape signing fingerprints
match. TLS-preserving direct resolution returned HTTP 200 with valid
certificates for `auth`, `login`, `lldap`, `pink`, and `pink-account`.
## T05 - Run full pre-cutover identity conformance
```task