Uploaded image for project: 'Red Hat Advanced Cluster Management'
  1. Red Hat Advanced Cluster Management
  2. ACM-12397

Make maestro addon as TP feature

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Critical Critical
    • ACM 2.12.0
    • ACM 2.12.0
    • Maestro
    • Make maestro addon as TP feature
    • False
    • None
    • False
    • Not Selected
    • To Do
    • ACM-12359 - Make maestro addon as TP feature
    • ACM-12359Make maestro addon as TP feature
    • 100% To Do, 0% In Progress, 0% Done

      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

      1. As a cluster admin, I can be able to enable the maestro addon in MCE CR.
      2. As a cluster admin, I can configure to use maestro to install all addons.

      Acceptance Criteria

      ...

      Dependencies (internal and external)

      1. ...

      Previous Work (Optional):

      1. ...

      Open questions:

      1. It depends on one centralized postgres
      2. How to bring the streams of apache Kafka (2.7)? install by maestro-addon-controller?
      3. how to install maestro-addon? use addon framework so that you can specify kube as workload driver.
      4. what scenario we propose to use maestro? > 1000 managed cluster. if the customer's managed clusters increase from 100 to 1000, how to migrate?
      5. first step to enable cluster-proxy / managedserviceaccount / workmgr to use maestro to install.

      #4 top priority need to resolve firstly.

      1. address scalability to use maestro. use BYO-postgres and BYO-kafka make sense.
      2. if enable maestro by default, what is benefit comparing with maestro.
        1. same arch
        2. easy to migrate

      gRPC -> Kafka

      P0:

      1. Wei to do scalablity test
      2. Chunlin to follow up the open questions
      3. Longlong gRPC
      4. 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.

            Unassigned Unassigned
            clyang82 Chunlin Yang
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: