From e3d20c4ddc590df4f739a60087ec1f081b0acb97 Mon Sep 17 00:00:00 2001
From: Pete Wall <pete.wall@grafana.com>
Date: Wed, 20 Nov 2024 09:43:51 -0600
Subject: [PATCH] PodLog objects always go onto the alloy instance, not
 alloy-logs. We should determine clustering based on alloy

Signed-off-by: Pete Wall <pete.wall@grafana.com>
---
 .../templates/alloy_config/_operator_objects.txt                | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/charts/k8s-monitoring-v1/templates/alloy_config/_operator_objects.txt b/charts/k8s-monitoring-v1/templates/alloy_config/_operator_objects.txt
index 5333a55d2..4e5922b96 100644
--- a/charts/k8s-monitoring-v1/templates/alloy_config/_operator_objects.txt
+++ b/charts/k8s-monitoring-v1/templates/alloy_config/_operator_objects.txt
@@ -139,7 +139,7 @@ loki.source.podlogs "podlogs_objects" {
 {{ .Values.logs.podLogsObjects.selector | indent 4 }}
   }
 {{- end }}
-{{- if (index .Values "alloy-logs").alloy.clustering.enabled }}
+{{- if .Values.alloy.alloy.clustering.enabled }}
   clustering {
     enabled = true
   }