-
Story
-
Resolution: Unresolved
-
Major
-
ACM 2.14.0
Value Statement
Currently, ACM search is getting VirtualMachine RBAC details from the aggregated api server when fine grained RBAC feature flag is enabled. Based on results from the aggregated API (and what permissions the logged in user has), search then displays VirtualMachine related results. This is limited to kubevirt.io resources currently. This story is to enhance what k8s objects the aggregated API is checking. These are the related resources that we need the aggregate API server to check in addition to the kubevirt roles:

Definition of Done for Engineering Story Owner (Checklist)
- ...
Development Complete
- The code is complete.
- Functionality is working.
- Any required downstream Docker file changes are made.
Tests Automated
- [ ] Unit/function tests have been automated and incorporated into the
build. - [ ] 100% automated unit/function test coverage for new or changed APIs.
Secure Design
- [ ] Security has been assessed and incorporated into your threat model.
Multidisciplinary Teams Readiness
- [ ] Create an informative documentation issue using the Customer
Portal Doc template that you can access from [The Playbook](
and ensure doc acceptance criteria is met.
- Call out this sentence as it's own action:
- [ ] Link the development issue to the doc issue.
Support Readiness
- [ ] The must-gather script has been updated.
- is related to
-
ACM-21974 Aggregate API Server - RBAC model refinement for all Kubernetes resources
-
- Backlog
-