Value Statement

Currently, we can deploy MCE standalone on OCP. By enhancing the MCE operator, we aim to expand this capability to support deploying MCE and its components on AKS clusters. It is crucial to ensure that MCE can be successfully deployed, uninstalled, and upgraded (if necessary) for customers utilizing AKS.

Definition of Done for Engineering Story Owner (Checklist)

• [ ] MCE standalone deployment on AKS is successful.
• [ ] MCE can be uninstalled without issues.
• [ ] MCE upgrades are performed successfully when required.

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.