Background

ACM ships 4 custom virt roles:

• kubevirt.io-acm-hub:admin
• kubevirt.io-acm-hub:view
• kubevirt.io-acm-managed:admin
• kubevirt.io-acm-managed:view

Problem Statement

Several use cases find these roles hard to use. The main issues are:

• Naming is difficult to understand - uses ACM concepts (hub vs managed) rather than virt-focused terminology
• Users struggle to map these roles to their actual virtualization use cases

Proposed Approach

• Role permissions will largely remain the same
• Focus on reorganization and renaming for better user experience
• Improve naming to fit actual virt use cases rather than ACM-specific concepts
• Align with Kubernetes RBAC best practices as much as possible

Tasks

1. CNV backend team holds a review session to brainstorm initial ideas
2. Create a Google Doc with the CNV roles change proposal
3. Gather input from stakeholders
4. Get Josh's final approval on the proposal
5. Implement approved changes

Definition of Done

• [ ] Review session completed with CNV backend team
• [ ] Google Doc created with reorganization proposal
• [ ] Stakeholder feedback incorporated
• [ ] Josh's approval obtained
• [ ] Changes implemented (if time permits in this task)