-
Epic
-
Resolution: Unresolved
-
Critical
-
ACM 2.12.0
Epic Goal
Make maestro addon as TP feature
Why is this important?
As a TP feature, it can be easy to enable and try. for example, we can use the maestro way for argcd pull model and policy.
Scenarios
- As a cluster admin, I can be able to enable the maestro addon in MCE CR.
- As a cluster admin, I can configure to use maestro to install all addons.
Acceptance Criteria
...
Dependencies (internal and external)
- ...
Previous Work (Optional):
- ...
Open questions:
- It depends on one centralized postgres
- How to bring the streams of apache Kafka (2.7)? install by maestro-addon-controller?
- how to install maestro-addon? use addon framework so that you can specify kube as workload driver.
- what scenario we propose to use maestro? > 1000 managed cluster. if the customer's managed clusters increase from 100 to 1000, how to migrate?
- first step to enable cluster-proxy / managedserviceaccount / workmgr to use maestro to install.
#4 top priority need to resolve firstly.
- address scalability to use maestro. use BYO-postgres and BYO-kafka make sense.
- if enable maestro by default, what is benefit comparing with maestro.
- same arch
- easy to migrate
gRPC -> Kafka
P0:
- Wei to do scalablity test
- Chunlin to follow up the open questions
- Longlong gRPC
- maestro-addon installation need to use addon-framework.
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.