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

Deploy scoped user-engine delivery lanes
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-08-13 17:34:29 +02:00
parent af8a6889d0
commit dbbccc1a80
5 changed files with 42 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

11
workplans/NK-WP-0024-user-engine-portal-integration-expansion.md
View file

@ -156,3 +156,14 @@ external-provider skips. NetKingdom's runtime manifest now declares both
cluster-local endpoints, separate Secret keys, and audit-core egress. The
remaining gate is custody delivery of those two scoped values, image publish,
rollout, and the combined live matrix.
2026-08-13 rollout: the scoped provider credentials were transferred entirely
through Kubernetes APIs into Secret `user-engine-delivery`, containing exactly
`event-token` and `mail-token`; no value was printed or persisted outside the
cluster. user-engine commit `a0f39f5` was published and deployed at immutable
digest `sha256:4eac10bf157e48eeadef16a2da83a00933914c9d37338f01679692008de21565`.
The rollout completed, `/readyz` reports all checks true, and in-pod probes
reach flex-auth, audit-core, and email-connect with HTTP 200 through the
declared NetworkPolicies. Remaining T04 evidence is application-level outbox
delivery and the negative matrix; health reachability alone is not reported
as delivery acceptance.