coulomb/net-kingdom
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
net-kingdom/sso-mfa/k8s/tenant-engine/README.md
tegwick 1c2d0c2cf6 Follow the access-engine CLI rename: ./cmd/flex-auth -> ./cmd/access-engine 
FLEX-DEC-2026-020; the old path is a stub that exits 2. Runtime names unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 736651@bnt-lap001
Assistant-Session: f6189624-fd64-4109-b53e-f8a59ca8a2d8
2026-10-10 15:28:05 +02:00

2 KiB
Raw Blame History

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, the chart name and the OCI package coordinate coulomb/flex-auth are unchanged (FLEX-DEC-2026-013). The CLI is now cmd/access-engine; cmd/flex-auth is a stub that exits 2 (FLEX-DEC-2026-020).

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.