Value Statement

This is first version of maestro addon controller. It won't provide capability to deploy maestro in this story. but it is ready for developing new features.

Definition of Done for Engineering Story Owner (Checklist)

• use helm chart to deploy maestro addon in multicluster-engine namespace (done)
• deploy the maestro-agent into managed cluster by using mca (done)
• the maestro addon controller repo is created in github.com/stolostron/maestro-addon
• provide document so that we can follow up the readme to deploy maestro addon (done)
• provide document how to modify clustermanager to enable to use maestro for manifestworkreplicaset controller (done)
• write end-to-end tests (done)

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.