Value Statement

To provide flexibility and control over their environments, we aim to enhance the MCE operator to support an uninstallation process from AKS clusters. This will enable users to completely remove their MCE deployments without leaving components or encountering errors, ensuring a clean and manageable cluster state post-uninstallation.

Definition of Done for Engineering Story Owner (Checklist)

• [ ] MCE operator initiates the uninstallation process correctly and transitions through all necessary steps without manual intervention.
• [ ] All MCE components, including CRDs, namespaces, and associated resources, are removed from the AKS cluster.

Development Complete

• The code is complete.
• Functionality is working.
• Any required downstream Docker file changes are made.

Tests Automated

• [ ] Unit/function tests have been automated and incorporated into the
  build.
• [ ] 100% automated unit/function test coverage for new or changed APIs.

Secure Design

• [ ] Security has been assessed and incorporated into your threat model.

Multidisciplinary Teams Readiness

• [ ] Create an informative documentation issue using the [Customer
  Portal_doc_issue template](
  https://github.com/stolostron/backlog/issues/new?assignees=&labels=squad%3Adoc&template=doc_issue.md&title=),
  and ensure doc acceptance criteria is met. Link the development issue to
  the doc issue.
• [ ] Provide input to the QE team, and ensure QE acceptance criteria
  (established between story owner and QE focal) are met.

Support Readiness

• [ ] The must-gather script has been updated.