-
Epic
-
Resolution: Unresolved
-
Normal
-
None
Epic Goal
- ACM can support ApplicationSet type Application Lifecycle Management on microshift
We need to achieve this with our Pull-Model approach https://cloud.redhat.com/blog/introducing-the-argo-cd-application-pull-controller-for-red-hat-advanced-cluster-management
Why is this important?
- microshift could be part of hybrid cloud blueprint
- microshift supports edge scenarios
- from data center to the edge customers want cluster has same application life cycle management
- currently .data.server field is empty in secret 'xxx-cluster-secret'
- https://microshift.io/docs/getting-started/
Scenarios
- ...
Acceptance Criteria
- CI - MUST be running successfully with tests automated
- Release Technical Enablement - Provide necessary release enablement details and documents.
- ...
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 - Downstream documentation merged: <link to meaningful PR>
- is related to
-
ACM-8836 Split policy generator manifests per policy by group or configurable constant
- New