Epic Goal

The goal of this Epic is to automatically deploy the ACM Right-Sizing solution as part of the ACM (MCO) deployment based on a configuration/feature flag
OBSDA-576  - 

Why is this important?

Currently, we have developed the ACM Right-Sizing dev preview solution at the namespace level, and users can deploy it manually by following the guidelines. We’ve received positive customer feedback so far, and several customers are waiting for the tech preview release of this feature. To onboard more customers, we plan to release the Tech Preview alongside the MCO/ACM release.   

Scenarios

...

Acceptance Criteria

• The ACM Right-Sizing Namespace solution should be enabled automatically based on the feature flag in MCO CRD. Users should not need to manually apply any YAML files to enable the Right-Sizing solution.
• Extend MCO codebase to add right-sizing namespace recommendation feature
• Write unit test cases for the added code, all CI test cases should be passed.
• User should be able to configure inlcude/exclude namespace, label criteria, recommendation percentage, placement via config.
• Required component should be reconciled if deleted or based on updated any configuration.
• Test changes by deploying custom image in ACM cluster setup before raising PR
• Get required approval from MCO team on PR and merge the changes.
• After code merge once we have ACM build test it out required feature working expected or not
• Give demo to wider audience

Dependencies (internal and external)

1. ...

Previous Work (Optional):

• Documentation around Right Sizing Dev Preview can be found here
• DDR for RightSizing Recommendation
• MultiCluster Observability Architecture Call DDR Discussion Recording
• MCME Core Architecture Meeting DDR Discussion Recording (26-min onwards)

Open questions:

1. …

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Doc issue opened with a completed template. Separate doc issue
  opened for any deprecation, removal, or any current known
  issue/troubleshooting removal from the doc, if applicable.
• Considerations were made for Extended Update Support (EUS)