chore(install): reduce default resource footprint

Author: squakez

docs/modules/ROOT/pages/installation/advanced/resources.adoc

@@ -30,11 +30,11 @@ The main Camel K Operator Pod contributor resources consumption is likely to be
 ```
 resources:
   requests:
-    memory: "4Gi"
-    cpu: "1"
+    memory: "2Gi"
+    cpu: "500m"
   limits:
-    memory: "16Gi"
-    cpu: "4"
+    memory: "8Gi"
+    cpu: "2"
 ```
 
 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.

pkg/resources/config/manager/operator-deployment.yaml

@@ -80,11 +80,11 @@ spec:
             periodSeconds: 10
           resources:
             requests:
-              memory: "4Gi"
-              cpu: "1"
+              memory: "2Gi"
+              cpu: "500m"
             limits:
-              memory: "16Gi"
-              cpu: "4"
+              memory: "8Gi"
+              cpu: "2"
           securityContext:
             runAsNonRoot: true
             seccompProfile:

script/Makefile

@@ -107,7 +107,7 @@ TEST_PREBUILD = build
 # Tests may run in parallel to each other. This count sets the amount of tests run in parallel.
 # (default value would be otherwise GOMAXPROCS)
 TEST_COMMON_PARALLEL_COUNT ?= 2
-TEST_ADVANCED_PARALLEL_COUNT ?= 2
+TEST_ADVANCED_PARALLEL_COUNT ?= 4
 
 # OLM (Operator Lifecycle Manager and Operator Hub): uncomment to override operator settings at build time
 #GOLDFLAGS += -X github.com/apache/camel-k/v2/pkg/util/olm.DefaultOperatorName=camel-k-operator