-
Epic
-
Resolution: Unresolved
-
Critical
-
None
Epic Goal
...
We have a documented limitation with the Pull-Model to deploy only to openshift-gitops namespace
This should be quite easy to change (e.g. https://access.redhat.com/solutions/6097231)
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. - Considerations were made for Extended Update Support (EUS)
- depends on
-
ACM-22707 Argocd Pull Model appset in any namespace implementation
-
- Resolved
-
-
ACM-22416 improve gitops addon startup duration
-
- Closed
-
-
ACM-22804 ArgoCD AppSet in any namespace design
-
- Closed
-
-
ACM-22549 investigate ArgoCD applicationset in any namespace
-
- Closed
-
- is duplicated by
-
ACM-20327 Ensure Applicationsets in any namespace works (Push and Pull)
-
- Closed
-
- is related to
-
ACM-25331 applicationSet in any namespace documentation
-
- Closed
-