This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
Bug 2221482 - Consider creating Role instead of ClusterRole for cross ns cloning
Summary: Consider creating Role instead of ClusterRole for cross ns cloning
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: Documentation
Version: 4.14.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Audrey Spaulding
QA Contact: Kevin Alon Goldblatt
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-07-09 11:36 UTC by Alex Kalenyuk
Modified: 2023-11-30 16:30 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-11-30 16:30:14 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   CNV-30799 0 None None None 2023-11-30 16:30:13 UTC

Description Alex Kalenyuk 2023-07-09 11:36:07 UTC 
Document URL: 
https://docs.openshift.com/container-platform/4.13/virt/virtual_machines/cloning_vms/virt-enabling-user-permissions-to-clone-datavolumes.html

Section Number and Name: 

Describe the issue: 
We could add a small note to consider creating `Role`
instead of `ClusterRole` where appropriate. We don't have to be super specific
but for completeness, the use case is a non-admin user that is an a admin of both source/target namespaces.

Suggestions for improvement: 

Additional information:
Note You need to log in before you can comment on or make changes to this bug.