-
Epic
-
Resolution: Unresolved
-
Major
-
None
-
None
-
RHACM Provide solution for Developer-Scenario
-
False
-
None
-
False
-
Not Selected
-
To Do
-
0
-
0%
Epic Goal
...
When talking about Application Deployments the question I get is:
What can RHACM do for my developers.
The answer could be: With Cluster as a Service in mind, create a ClusterSet for developers, allow UI access but only allow Deployments into a namespace and to Clusters in the Developer Clusterset.
It fails so far to have the correct ClusterRole
Why is this important?
...
Scenarios
...
Acceptance Criteria
...
Dependencies (internal and external)
- ...
Previous Work (Optional):
- ...
Open questions:
- …
Done Checklist
- CI - CI is running, tests are automated and merged.
- Release Enablement <link to Feature Enablement Presentation>
- DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
Issue> - DEV - Upstream documentation merged: <link to meaningful PR or GitHub
Issue> - DEV - Downstream build attached to advisory: <link to errata>
- QE - Test plans in Polarion: <link or reference to Polarion>
- QE - Automated tests merged: <link or reference to automated tests>
- DOC - Doc issue opened with a completed template. Separate doc issue
opened for any deprecation, removal, or any current known
issue/troubleshooting removal from the doc, if applicable.
