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

As a cluster admin, I can be able to deploy the controlplane agent in hosted mode.

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Blocker Blocker
    • None
    • None
    • xCM
    • None
    • controlplane_hosted_mode
    • False
    • None
    • False
    • Not Selected
    • To Do
    • ACM-3976 - Next iteration of ACM in ROSA
    • ACM-3976Next iteration of ACM in ROSA

      OCP/Telco Definition of Done
      <https://docs.google.com/document/d/1TP2Av7zHXz4_fmeX4q9HB0m9cqSZ4F6Jd4AiVoaF_2s/edit#heading=h.gaa58bzbvwde>
      Epic Template descriptions and documentation.
      <https://docs.google.com/document/d/14CUCEg6hQ_jpsFzJtWo29GfFVWmun2Uivrxq3_Fkgdg/edit>
      ACM-wide Product Requirements (Top-level Epics)
      <https://docs.google.com/document/d/1uIp6nS2QZ766UFuZBaC9USs8dW_I5wVdtYF9sUObYKg/edit>

      *<--- Cut-n-Paste the entire contents of this description into your new
      Epic --->*

      Epic Goal

      for SD case, the controlplane is running in the management cluster. the controlplane agent should be running in the management cluster as well. In order to support this case, we need to have controlplane agent run in the management cluster to provide the same capabilities like default mode provides.

      Why is this important?

      Reduce the footprint of ACM in ROSA case.

      Scenarios

      ...

      Acceptance Criteria

           1. the controlplane agent can be deployed in the management cluster.

           2. the configuration policy can be executed as normal

           3. Need a simple e2e case to cover this scenarios

           4. Need write down a document what is required to enable controlplane agent in hosted mode.

           5.

      Dependencies (internal and external)

      1. ...

      Previous Work (Optional):

      1. ...

      Open questions:

      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 - Downstream documentation merged: <link to meaningful PR>

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

                Created:
                Updated:
                Resolved: