-
Epic
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
ACS authz configuration cannot be inherited from the OCP's one
-
Product / Portfolio Work
-
False
-
-
False
-
Not Selected
-
To Do
-
ROX-29033 - RBAC Alignment between ACS, ACM and OCP
-
-
-
Overview:
This is an understandable hurdle for users, as they need to set up individual OCP (and kubernetes) clusters first, and then configure authz again in ACS (and ACM). A "one-window access configuration" would help. The multicluster and multiproduct authz is a prerequisite we need to figure out here (for entire OCP portfolio I'd say).
Requirements:
TBD
Technical Scope:
High-level list of items that are in scope; usually completed by a staff engineer or a lead from the Feature Delivery Team. Initial completion during Refinement status.
TBD
Out of Scope:
High-level list of items that are out of scope. Initial completion during Refinement status.
TBD
Outstanding Questions (Optional):
Include a list of refinement / architectural questions that may need to be answered before coding can begin. Initial completion during Refinement status.
<your text here>