From b7f2bc68a9ee5597390679187a7d23fb23a74740 Mon Sep 17 00:00:00 2001 From: duynguyen Date: Sun, 3 May 2026 15:44:40 +0700 Subject: [PATCH] fix: update serviceMonitor and podMonitor selector configurations Changed serviceMonitorSelectorNilUsesHelmValues and podMonitorSelectorNilUsesHelmValues from true to false in values.yaml to ensure explicit selection of ServiceMonitors and PodMonitors for Prometheus target discovery. --- manifest/kube-prometheus-stack/values.yaml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/manifest/kube-prometheus-stack/values.yaml b/manifest/kube-prometheus-stack/values.yaml index db460cd..589ebe1 100644 --- a/manifest/kube-prometheus-stack/values.yaml +++ b/manifest/kube-prometheus-stack/values.yaml @@ -4308,7 +4308,7 @@ prometheus: ## prometheus resource to be created with selectors based on values in the helm deployment, ## which will also match the servicemonitors created ## - serviceMonitorSelectorNilUsesHelmValues: true + serviceMonitorSelectorNilUsesHelmValues: false ## ServiceMonitors to be selected for target discovery. ## If {}, select all ServiceMonitors @@ -4331,7 +4331,7 @@ prometheus: ## prometheus resource to be created with selectors based on values in the helm deployment, ## which will also match the podmonitors created ## - podMonitorSelectorNilUsesHelmValues: true + podMonitorSelectorNilUsesHelmValues: false ## PodMonitors to be selected for target discovery. ## If {}, select all PodMonitors