Uploaded image for project: 'Ansible Automation Platform RFEs'
  1. Ansible Automation Platform RFEs
  2. AAPRFE-1471

Ability to specify request and limits for the different controllers created by AAP

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • 2.4
    • None
    • False
    • Hide

      None

      Show
      None
    • False

      What is the nature and description of the request?
      Ansible Automation Platform (AAP) can be installed in OpenShift Container Platform 4 and by default all controller pods created in the aap namespace even have requests and limits applied. Depending on the size of the environment and activity run with AAP, those value may need to be changed to either increase them or even lower them (rare situation). This though is not possible today. A change can only be applied, using the Subscription Resource for the Operator (see AAP-9444 and AAP-4589). Even though the approach via Subscription is working, it's not really practical as it changes the values for all controllers run by AAP. This means massive amount of resources are wasted, when for example only the eda-controller resource request and limit need to be changed. The current approach would increase it for all controllers, which in turn means more infrastructure cost and those are considered wasted as beside the eda-controller for example, the others won't require the change.
       
      Why does the customer need this? (List the business requirements here)
      It's generally a matter of cost and waste of resource. This boils down to sustainability objects and budget constrains. It's therefore key to have a way to control request and limits for all different controllers separately to prevent issues from happening and resources being wasted.

      How would you like to achieve this? (List the functional requirements here)
      It should be possible, when deploying a specific component such as automation-controller, automation-hub, eda-controller, etc. to specify the request and limits for the said controller. That way, one can increase/adjust the values if and where needed, without impacting the other controllers that may be running fine with the values set.

      While AAP is not a OpenShift Container Platform 4 - Cluster component, Resources and Limits could be evaluated. Also most customers won't appreciate such an approach but one could use that document to at least have some reasoing on that decision.

      List any affected known dependencies: Doc, UI etc..

      • Ansible Automation Platform (AAP) - Operator
      • Automation Controller
      • Automation Hub
      • EDA Controller
      • etc.
      • Documentation

      Github Link if any
      N/A but AAPRFE-620 looks very similar

            bcoursen@redhat.com Brian Coursen
            rhn-support-sreber Simon Reber
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: