Uploaded image for project: 'Red Hat Fuse'
  1. Red Hat Fuse
  2. ENTESB-14015

Unable to set CPU requests and limits for Components and Integrations

    XMLWordPrintable

Details

    • Feature Request
    • Status: Done
    • Critical
    • Resolution: Done
    • fuse-7.6-GA
    • fuse-7.8-GA
    • Fuse Online

    Description

      LimitRange are automatically applied to all the pods that don't define resources (requests/limits). Currently, you can only set memory limits for some Syndesis components. The most heavy component is syndesis-server which, by default, requires 450m of CPU with a limit of 750m.

      Now, if you are on a shared cluster with LimitRange, you are forced to set a CPU request which is equal to the most heavy pod (component or integration), but this is then requested by all pods. We need a way to set specific CPU/mem values for all pods created by Syndesis at the CR level and also a way to set specific resources for some heavy integrations.

      Attachments

        Activity

          People

            kstam@redhat.com Kurt Stam
            rhn-support-fvaleri Federico Valeri
            Andrej Vano Andrej Vano
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: