Details
-
Enhancement
-
Resolution: Won't Do
-
Major
-
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
How
Requests and limits for the CPU and memory should be set for the build and builder pods.