OCP/Telco Definition of Done
Epic Template descriptions and documentation.
<--- Cut-n-Paste the entire contents of this description into your new Epic --->
Epic Goal
- Support Syncsets for all Kubernetes targets via a secret only.
- Do not require ClusterDeployment (though if its merited, I could see including this)
- This helps ACM algin to a single method of bootstrapping clusters
Why is this important?
- Single method, instead of ACM creating its own for bootstrapping
Scenarios
- I want to import a cluster into ACM, I need to bootstrap the agent. Use a syncset to do the bootstrap (push) of required Kube resources.
- Continue the import of new Hive provisioned clusters into ACM via syncset bootstrap (done today)
Acceptance Criteria
- Syncset works against any kube cluster, with minimal number of objects for scale.
Dependencies (internal and external)
- ACM Applier?
- ClusterDeployment object
Previous Work (Optional):
- …
Open questions::
- Do we need to keep ClusterDeployment
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>