Refactoring Role-based Access Control
Current implementation of RBAC injects a separate clusterrole and clusterrolebinding with its own secret per chart. This leads to a few issues, to name a few: (a) resources are orphaned when charts are deleted; (b) role name collision as clusterroles are not namespaced. This BP proposes to remove the additional role and add namespace separation as well as remove resources that the roles do not need access for to enforce principle of least privilege.
Blueprint information
- Status:
- Not started
- Approver:
- Steve Wilkerson
- Priority:
- Undefined
- Drafter:
- Tin Lam
- Direction:
- Approved
- Assignee:
- Tin Lam
- Definition:
- Review
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
WIP: RBAC for OSH
Addressed by: https:/
RBAC: fix chart to be consistent with others
Addressed by: https:/
RBAC: Fix issue with inclusion of empty jobs or daemonsets
Addressed by: https:/
RBAC: Fix issue with inclusion of empty jobs or daemonsets
Addressed by: https:/
Ceilometer: RBAC for helm test