Open security core for dev sec ops on kubernetes
Settles two questions raised by bringing NetKingdom under Railiance governance: 1. Separate rapp-* repos per engine (rapp-tenant-engine, rapp-user-engine), following repository-axes.md's one-workload rule. The decisive property is independent rollback -- a single rapp would need one rollback contract across independently versioned services. secrets-engine is not packaged as a rapp: it has no deployed workload. 2. CloudNative PG via rapp-postgres is the default relational platform for production. Per-workload SQLite-on-a-PVC is dev/test only, and rail-kubernetes wave-1 does not support the persistent-storage contract it depends on. tenant-engine migrates; its TenantStore Protocol makes this a backend swap behind an existing seam. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> |
||
|---|---|---|
| .claude | ||
| .forgejo/workflows | ||
| .githooks | ||
| canon | ||
| docs | ||
| examples | ||
| history | ||
| identity-provisioner | ||
| keys | ||
| local-identity | ||
| registry | ||
| sso-mfa | ||
| tests | ||
| tools | ||
| wiki | ||
| workplans | ||
| .custodian-brief.md | ||
| .gitignore | ||
| .repo-classification.yaml | ||
| .sops.yaml | ||
| AGENTS.md | ||
| CLAUDE.md | ||
| CONFIG.md | ||
| DECISIONS.md | ||
| INTENT.md | ||
| LICENSE | ||
| Makefile | ||
| README.md | ||
| SCOPE.md | ||
| WORK-RECORDS.md | ||
NetKingdom
NetKingdom provides a dynamic self optimizing full circle security-platform for kubernetes deployed IT-infrastructures.
Orientation
- SCOPE.md — what this repo owns, current state, and when it is relevant
Security Infrastructure Documents
- secrets-engine security infrastructure boundary defines how secrets-engine participates in the NetKingdom security infrastructure and how it interacts with OpenBao, flex-auth, user-engine, ops-warden, ops-bridge, info-tech-canon, State Hub, and agents.