Helm chart: allow setting limits to beyla cache

charts/beyla/Chart.yaml

@@ -1,6 +1,6 @@
 apiVersion: v2
 name: beyla
-version: 1.4.8
+version: 1.4.9
 appVersion: 1.8.6
 description: eBPF-based autoinstrumentation HTTP, HTTP2 and gRPC services, as well as network metrics.
 home: https://grafana.com/oss/beyla-ebpf/

charts/beyla/templates/cache-deployment.yaml

@@ -49,6 +49,10 @@ spec:
               containerPort: {{ .Values.k8sCache.profile_port }}
               protocol: TCP
           {{- end }}
+          {{- with .Values.k8sCache.resources }}
+          resources:
+            {{- toYaml . | nindent 12 }}
+          {{- end }}
           env:
             - name: BEYLA_K8S_CACHE_PORT
               value: "{{ .Values.k8sCache.service.port }}"

charts/beyla/values.yaml

@@ -292,6 +292,17 @@ k8sCache:
     #    secretKeyRef:
     #      name: secret-name
     #      key: value_key
+  resources: {}
+    # We usually recommend not to specify default resources and to leave this as a conscious
+    # choice for the user. This also increases chances charts run on environments with little
+    # resources, such as Minikube. If you do want to specify resources, uncomment the following
+    # lines, adjust them as necessary, and remove the curly braces after 'resources:'.
+    # limits:
+    #   cpu: 100m
+    #   memory: 128Mi
+    # requests:
+    #   cpu: 100m
+    #   memory: 128Mi
   image:
     # -- K8s Cache image registry (defaults to docker.io)
     registry: "docker.io"

cmd/k8s-cache/main.go

@@ -7,6 +7,7 @@ import (
 	"io"
 	"log/slog"
 	"net/http"
+	_ "net/http/pprof"
 	"os"
 	"os/signal"
 	"syscall"