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

• Do not leave payloads behind when syncsets are delete.
• Similar to the Argo Prune option.

Why is this important?

• In Baremetal, where deleting a ClusterDeployment leaves the nodes as is, anything deployed with a SyncSet is still running. This has security implications, and is poor optics.

Scenarios

1. Delete a bare metal cluster.  ACM agent remains and is still trying to talk to the ACM hub
2. I delete a BM cluster, but the trading application I activated using a syncset is still running
3. I delete a BM cluster but the IAM configuration is still in place because the SyncSet left it.

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• Either delete payload or disable the BM cluster

Dependencies (internal and external)

1. Bare Metal

Previous Work (Optional):

1. …

Open questions::

1. Could we power off the BM cluster on ClusterDeployment delete (this gives us a similar activity to deleting cloud provider cluster VM's)

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>