-
Epic
-
Resolution: Unresolved
-
Major
-
None
Epic Goal
...
let the user hint ACM on how to aggregate applications. For example there could be a label such as apps.open-cluster-management.io/multicluster-app-name: xyz. ACM will discover the xyz app and aggregate it. This way it does not matter how the xyz app was created. This will give value to ACM irrespective of what deployment mechanisms were used for apps.
Why is this important?
...
gives more flexibility, feedback from the field
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.
