feat: add clusterAccess option for Kubernetes RBAC #18
Reference in New Issue
Block a user
Delete Branch "feat/cluster-access-rbac"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Adds a
clusterAccessvalue to the Helm chart that controls what Kubernetes RBAC is provisioned for the devcontainer pod.none(default)readonlynsreadwritensreadonlyreadwriteThe ServiceAccount is bound to the Deployment via
serviceAccountNamewheneverclusterAccess != none.Usage
Test plan
helm templatewith each access level renders expected resourcesclusterAccess: none(default) produces no ServiceAccount/Role/Binding resourcesreadonlyns— confirm pod cankubectl get pods -n <ns>but not cluster-widereadonly— confirm pod cankubectl get nodesnone— confirm no cluster API access🤖 Generated with Claude Code