Open security core for dev sec ops on kubernetes
Once any admin policy exists, PI enforces it for all admins. Without an explicit policy, pi-admin is locked out of the REST API after trigger-admin-rights is created. Add pi-admin-all-rights (scope=admin, action=*) via pi-manage (in-pod) as step 5, before the REST-based trigger-admin-rights step. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> |
||
|---|---|---|
| .claude/commands | ||
| .githooks | ||
| canon/standards | ||
| docs | ||
| keys | ||
| local-identity | ||
| sso-mfa | ||
| wiki | ||
| workplans | ||
| .gitignore | ||
| .sops.yaml | ||
| CLAUDE.md | ||
| CONFIG.md | ||
| DECISIONS.md | ||
| LICENSE | ||
| Makefile | ||
| README.md | ||
| SCOPE.md | ||
NetKingdom
NetKingdom provides a dynamic self optimizing full circle security-platform for kubernetes deployed IT-infrastructures.