Epic Goal

Enhance synchronization between the MCE operator and its components by creating a InternalEngineComponent CRD. This CRD will allow for precise determination of dependencies before deleting resources or proceeding with uninstallation.

Why is this important?

The introduction of the InternalEngineComponent CRD is crucial for improving the management and synchronization of sub-components within the MCE operator. By establishing clear dependencies, this CRD will:

• Ensure proper cleanup of components before deletion, preventing resource leaks and potential errors.
• Facilitate smoother uninstallation and disabling processes by identifying components that need to be handled first.
• Enhance the reliability and efficiency of the MCE operator, leading to better overall system stability.
• Provide squads with a more streamlined and predictable workflow, reducing the chances of unintended disruptions during component updates or removals.

Scenarios

...

Acceptance Criteria

...

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. ...

Open questions:

1. …

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.