Value Statement

To ensure our customers can benefit from the latest features and improvements, we aim to enhance the MCE operator to support smooth and reliable upgrades on AKS clusters. This will enable users to upgrade their existing MCE deployments to new versions without encountering disruptions or errors, thereby maintaining performance and functionality.

Definition of Done for Engineering Story Owner (Checklist)

• [ ] MCE operator successfully detects when a new version is available.
• [ ] Upgrade process initiates correctly and transitions through all necessary steps without manual intervention.
• [ ] The MCE operator completes the upgrade to the new version without errors.

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.