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

Build a single core agent that is usable for MCE & ACM

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Duplicate
    • Icon: Normal Normal
    • None
    • None
    • Server Foundation
    • Reduce agent footprint
    • False
    • None
    • False
    • Not Selected
    • To Do

      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

      Telco, MCE, ACM & MicroShift.

      Using what we learned from NextGen Control Plane we want to shrink the agent.  This is a good next step after ACM-5552 is complete.

      Why is this important?

      Size of the Agent and Control Plane is under a microscope in Managed offerings. As well in Telco and MicroShift where resources on the ManagedCluster are in short supply.

      Agent size determines whether ACM will be used in the solution or not.

      Scenarios

      1. Core klusterlet, registration and work should be combined for use in ACM and MCE

      Acceptance Criteria

      Agent shows reduced footprint

      Dependencies (internal and external)

      1. NextGen Control Plane work on footprint reduction complete
      2. ACM-5552 complete (consolidate repositories)

      Previous Work (Optional):

      NA

      Open questions:

      1. How What is the final size:
        1. memory
        2. image
      1. Delta size
        1. Original memory for all pods
        2. original image sizes

      Done Checklist

      • CI - CI is running, tests are automated and merged.
      • 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>
      •  

              leyan@redhat.com Le Yang
              jpacker@redhat.com Joshua Packer
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: