Skip to content

docs(readme): give the deployer role explicit verbs - #50

Merged
lhoupert merged 1 commit into
mainfrom
docs/deployer-role-explicit-verbs
Nov 10, 2026
Merged

lhoupert merged 1 commit into
mainfrom
docs/deployer-role-explicit-verbs

Conversation

@lhoupert

Copy link
Copy Markdown
Contributor

The deployer Role in "Kubernetes cluster setup" granted *. On roles and rolebindings that includes escalate and bind, so a leaked deploy token could grant itself any permission in the namespace. The verbs are now listed: same resources, and still enough for the deploy workflow, since the mcp-index Role it creates only grants permissions the deployer already holds.

For reviewers: this changes new setups only. An existing instance keeps its Role until someone edits it (kubectl -n <namespace> edit role deployer).

How this was made

Claude Code drafted the change; @lhoupert asked for it and approved the diff. The README command as written was run as a server-side dry run against a cluster running this template, and it creates the Role with the listed verbs. With the same Role, impersonating deployer: escalate and bind are refused, and creating the mcp-index Role and RoleBinding still works. A real CI deploy with it has not run yet.

— Claude Code, on behalf of @lhoupert

`*` on roles and rolebindings includes escalate and bind.
@ciaransweet
ciaransweet force-pushed the docs/deployer-role-explicit-verbs branch from 22a414b to 362829d Compare November 10, 2026 14:02
@lhoupert
lhoupert merged commit cc2b529 into main Nov 10, 2026
9 checks passed
@lhoupert
lhoupert deleted the docs/deployer-role-explicit-verbs branch November 10, 2026 14:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants