History

tegwick 0db2e1404d All checks were successful CI Smoke / host-smoke (push) Successful in 0s Details CI Smoke / container-smoke (push) Successful in 2s Details NK-WP-0039-T04: retire runtime.yaml to owner pointers; finish NK-WP-0039 tenant-engine disposition TEN-DEC-2026-003. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Assistant: claude-code Assistant-Model: sonnet Assistant-Process: 6969@bnt-lap001 Assistant-Session: e8ae73f2-8385-4c9c-b714-94c3c52cdbc0		2026-10-01 21:38:03 +02:00
..
README.md	NK-WP-0039-T04: retire runtime.yaml to owner pointers; finish NK-WP-0039	2026-10-01 21:38:03 +02:00
runtime.yaml	NK-WP-0039-T04: retire runtime.yaml to owner pointers; finish NK-WP-0039	2026-10-01 21:38:03 +02:00

README.md

Tenant Engine integration references

runtime.yaml is retired and now holds pointers only, no Kubernetes objects (NK-WP-0039-T04, 2026-10-01). NetKingdom does not own the Tenant Engine or flex-auth runtime (ADR-0015); do not recreate a copy here.

Tenant Engine: deploy/base/tenant-engine.yaml (kubectl apply -k deploy/) with the promotion contract in railiance/app.toml (TEN-DEC-2026-003).

The flex-auth objects were removed on 2026-09-28 with the owner's agreement. For flex-auth consumers use the owner's maintained declarations and deployment procedure:

Consumer	Authoritative values in the flex-auth repository
Tenant Engine	values/tenant-engine.yaml
User Engine	values/user-engine.yaml

The owner Helm chart renders the consumer Deployment, Service and NetworkPolicy, including caller-auth configuration. Both reviewed value files select enforcement and bind the consumer to its own Kubernetes ServiceAccount. Keep those settings at their owner; do not recreate a frozen deployment copy here.

These links assume sibling checkouts. The repository is coulomb/access-engine (formerly coulomb/flex-auth; same Forge ID, renamed under FLEX-WP-0020). The product and runtime names stay flex-auth: the flex-auth namespace, Service DNS, caller-token audience, cmd/flex-auth, the chart name and the OCI package coordinate coulomb/flex-auth are unchanged (FLEX-DEC-2026-013).

Ownership follows ADR-0015. Removing references requires no cluster apply or rollout. Do not use the remaining YAML as a way to provision the two flex-auth consumers.