add chart option for cluster-collector to set cache-maxsize if a k8s-…

…cluster generate more than 10000 metrics
Checkmk · May 22, 2024 · 056664f · 056664f
1 parent de7b781
commit 056664f
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 0 deletions.
diff --git a/deploy/charts/checkmk/templates/cluster-collector-deploy.yaml b/deploy/charts/checkmk/templates/cluster-collector-deploy.yaml
@@ -47,6 +47,7 @@ spec:
           args:
             - "--log-level={{ .Values.clusterCollector.logLevel }}"
             - "--address={{ default "0.0.0.0" .Values.clusterCollector.address }}"
+            - "--cache-maxsize={{ defaulut "10000" .Values.clusterCollector.cacheMaxsize }}"
             - "--reader-whitelist={{ .Release.Namespace }}:{{ template "checkmk.serviceAccountName.checkmk" . }}"
             - "--writer-whitelist={{ .Release.Namespace }}:{{ template "checkmk.serviceAccountName.nodeCollector.containerMetricsCollector" . }},{{ .Release.Namespace }}:{{ template "checkmk.serviceAccountName.nodeCollector.machineSectionsCollector" . }}"
           {{- if .Values.tlsCommunication.enabled }}

diff --git a/deploy/charts/checkmk/values.yaml b/deploy/charts/checkmk/values.yaml
@@ -97,6 +97,9 @@ clusterCollector:
   # can be: "debug", "info", "warning" (default), "critical"
   logLevel: warning
 
+  # cacheMaxsize set the maximum number of metric entries the cluster collector can hold at a time
+  cacheMaxsize: "10000"
+
   podAnnotations: {}
 
   podSecurityContext: {}