Value Statement

As a ACM user , I specify only a namespace for which I want Right sizing recommendation. This will be a wrapper around createExperiment API

• computeRecommendation ACM API will take the following json format as input { clusterName: String - Required, nameSpace : String - Optional application : String - Optional, measurement_duration - "minutes/days" }
• POC will only support namespace level recommendations .
• For workloads ( Deployments/Statefulset/DaemonSets) , get the containerNames
• form Kruize createExperimentObject

• Implement REST API computeRecommendation

Definition of Done for Engineering Story Owner (Checklist)

• ...

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.