-
Epic
-
Resolution: Unresolved
-
Major
-
None
-
None
-
ACM enable the import of ClusterProfiles into the ArgoCD cluster registry
-
False
-
None
-
False
-
Not Selected
-
To Do
Epic Goal
...
Our goal is to eventually contribute to the ArgoCD Operator, enabling the import of ClusterProfiles into the ArgoCD cluster registry.
Relevant URLs:
- https://github.com/kubernetes-sigs/cluster-inventory-api
- https://github.com/kubernetes/enhancements/pull/4778
- https://github.com/argoproj-labs/argocd-operator/issues/957
Why is this important?
...
Leverage the ongoing cluster-inventory-api and cluster profile work we've been doing in SIG-MC. Goal here is for OCM-io to populate cluster profile objects. With these SIG-MC objects, we can contribute to ArgoCD and propose they import this neutral SIG-MC API (instead of asking them to import OCM-io/ACM APIs, which they’ve already declined). This would enable the ArgoCD operator to directly import OCM-io/ACM managed clusters into ArgoCD's internal cluster registry.
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.
