Epic Goal

• To implement the uninstallation mechanism of the operator

Why is this important?

• When the operand is undeployed, it can happen that some pods are left unscheduled and gated until the user manually remove the scheduling gate. Using a proper mechanism to leave the controller running until (a) the webhook is removed, and (b) all the pods are ungated

Scenarios
1. …

Acceptance Criteria

• There is a clear path defined for the users that doesn't require them to manually patch and remove the scheduling gate from gated pods

Dependencies (internal and external)
1. …

Previous Work (Optional):
1. …

Open questions::
1. …

Done Checklist

• CI - For new features (non-enablement), existing Multi-Arch CI jobs are not broken by the Epic
• Release Enablement: <link to Feature Enablement Presentation>
• DEV - To design and implement the feature
• QE - Test cases are designed and automated in the e2e suite
• DOC - The uninstallation procedure is well-documented and the previous workaround with the CLI command to unpatch pods is removed from the next release's doc
• All the stories, tasks, sub-tasks and bugs that belong to this epic need to have been completed and indicated by a status of 'Done'.