You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: docs/modules/ROOT/pages/installation/advanced/resources.adoc
+25-9
Original file line number
Diff line number
Diff line change
@@ -34,25 +34,41 @@ The option accept a value in the following format `Key[=Value]:Effect[:Seconds]`
34
34
While installing the Camel K operator, you can also specify the resources requests and limits to assign to the operator `Pod` with `--operator-resources` option. The option will expect the configuration as required by https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/[Kubernetes Resource Management].
The value expected by the option are in the form `requestType.requestResource=value` where `requestType` must be either `requests` or `limits`, `requestResource` must be either `cpu` or `memory` and `value` expressed in the numeric value as expected by the resource. You can specify more than one `operator-resources`.
41
41
42
42
NOTE: if you specify a limit, but does not specify a request, Kubernetes automatically assigns a request that matches the limit.
43
43
44
-
=== Suggested configuration
44
+
=== Default Operator Pod configuration
45
45
46
-
The main contributor to compute resources consumption is likely to be the Maven builds that are performed in the operator `Pod` (assuming you use the default build strategy). So the resource requirements should be defined accordingly. The following requirements are sensible defaults that should work in most cases:
46
+
The main Camel K Operator Pod contributor resources consumption is likely to be the number of parallel builds that are performed in the operator `Pod`. So the resource requirements should be defined accordingly. The following requirements are sensible defaults that should work in most cases:
47
47
48
48
```
49
49
resources:
50
-
limits:
51
-
cpu: "1"
52
-
memory: 1Gi
53
50
requests:
54
-
cpu: 500m
55
-
memory: 512Mi
51
+
memory: "4Gi"
52
+
cpu: "1"
53
+
limits:
54
+
memory: "16Gi"
55
+
cpu: "4"
56
56
```
57
57
58
-
Note that if you plan to perform **native builds**, then the memory requirements must be increased significantly. Also, the CPU requirements are rather "soft", in the sense that it won't break the operator, but it'll perform slower in general.
58
+
Note that if you plan to perform **native builds**, then the memory requirements may be increased significantly. Also, the CPU requirements are rather "soft", in the sense that it won't break the operator, but it'll perform slower in general.
59
+
60
+
=== Default Integration Pod configuration
61
+
62
+
The resource set on the container here is highly dependant on what your application is doing. You can control this behavior by setting opportunely the resources on the Integration via container trait.
63
+
64
+
Be aware that the default are actually the following:
0 commit comments