Value Statement

Thanos has a lot of customization options, some of which can be used in specific situations to handle issues with specific customer environments (as an example: ACM-5860) . In order for customers be able to fine-tune installations, with the help of Red Hat Support, we would like to allow overwriting the Thanos components CLI arguments from within MCO. As there are too many configuration options available, and often these options are needed only for specific customers, it is not practical to start exposing these manually.

Definition of Done for Engineering Story Owner (Checklist)

• All Thanos components CLI args can be overwritten from the MCO CRD

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.