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

[Sizing] Specify builder and build pod requests and limits

    Details

    • Type: Task
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Camel-K
    • Labels:
      None

      Description

      What

      Currently, no requests or limits for CPU and memory are set for the builder and integration kit build pods. These are a lower priority than the requests and limits for the operator itself since they are short-lived but would still be useful to ensure Kubernetes will schedule the pod to a node with the required resources available.

      I would advise running load tests against the Camel K to determine a more realistic usage to base the requests and limits on.

      Current QoS class

      Best Effort

      How

      Requests and limits for the CPU and memory should be set for the build and builder pods.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                dffrench David Ffrench
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated: