Epic Goal
- Today we use SyncSets to bootstrap ACM Agents for Hive provisioned clusters (auto-import
- We want to extend SyncSet to work with non-hive clusters to create a single import path for ACM Managed-Cluster
Why is this important?
- One code path for import for ACM
- Hive users will be able to use SyncSet against any cluster.
Scenarios
- Put our default import resources into a syncset and target any cluster for Attach to ACM.
Acceptance Criteria
- CI - MUST be running successfully with tests automated
- Release Technical Enablement - Provide necessary release enablement details and documents.
- ...
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>
There are no Sub-Tasks for this issue.