• BU Product Work
    • False
    • Hide

      None

      Show
      None
    • False
    • 6
    • 0
    • Program Call

      Feature Overview (aka. Goal Summary)  

      Cluster Autoscaler and Karpenter are both Kubernetes autoscaling solutions, but they handle node scaling differently and have different approaches to integrating with DRA (Dynamic Resource Allocation).This feature is used to track the future investigations in integrating DRA with both the solutions.

      Requirements (aka. Acceptance Criteria):

       

      Anyone reviewing this Feature needs to know which deployment configurations that the Feature will apply to (or not) once it's been completed.  Describe specific needs (or indicate N/A) for each of the following deployment scenarios. For specific configurations that are out-of-scope for a given release, ensure you provide the OCPSTRAT (for the future to be supported configuration) as well.

      Deployment considerations List applicable specific needs (N/A = not applicable)
      Self-managed, managed, or both managed ROSA HCP
      Classic (standalone cluster)  
      Hosted control planes yes
      Multi node, Compact (three node), or Single node (SNO), or all MNO
      Connected / Restricted Network Connected
      Architectures, e.g. x86_x64, ARM (aarch64), IBM Power (ppc64le), and IBM Z (s390x) x86_x64, ARM (aarch64)
      Operator compatibility  
      Backport needed (list applicable versions) No
      UI need (e.g. OpenShift Console, dynamic plugin, OCM) yes - console
      Other (please specify) rosa-cli

      Use Cases (Optional):

      Include use case diagrams, main success scenarios, alternative flow scenarios.  Initial completion during Refinement status.

      <your text here>

      Questions to Answer (Optional):

      Include a list of refinement / architectural questions that may need to be answered before coding can begin.  Initial completion during Refinement status.

      <your text here>

       

      Out of Scope

      High-level list of items that are out of scope.  Initial completion during Refinement status.

      •  

      Background

      Provide any additional context is needed to frame the feature.  Initial completion during Refinement status.

       

      Customer Considerations

      Provide any additional customer-specific considerations that must be made when designing and delivering the Feature.  Initial completion during Refinement status.

      <your text here>

      Documentation Considerations

      Provide information that needs to be considered and planned so that documentation will meet customer needs.  If the feature extends existing functionality, provide a link to its current documentation. Initial completion during Refinement status.

       

      Interoperability Considerations

      Which other projects, including ROSA/OSD/ARO, and versions in our portfolio does this feature impact?  What interoperability test scenarios should be factored by the layered products?  Initial completion during Refinement status.

      <your text here>

              rh-ee-smodeel Subin M
              rh-ee-smodeel Subin M
              Michael McCune, Subin M
              Russell Teague Russell Teague
              Jeana Routh Jeana Routh
              Michael McCune Michael McCune
              Subin M Subin M
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: