From 3bf986825119cdb7bf787516922109854b84af43 Mon Sep 17 00:00:00 2001
From: thilak <thilak@base14.io>
Date: Thu, 24 Sep 2026 14:34:21 +0530
Subject: [PATCH 1/2] Correct the Windows section: supplied configs need a
 Windows config too

The section said the Windows daemon shares credentials with the other
collectors and there was nothing further to configure. That is only true when
the chart generates your collector configuration.

If you supply scout.agent.config or scout.daemon.config -- which is what the
otelcol style configuration further down this page does -- your configuration
carries its own credentials under value names you chose, commonly
scout.clientId and scout.clientSecret. A generated Windows configuration would
instead derive client_id from scout.appName and read the secret from
scout.apiKey, so the Windows daemon would authenticate differently from every
other collector in the release.

Chart 0.6.1 refuses to render in that case rather than doing it silently. This
documents the requirement and shows the configuration to supply.

extraEnvs is described alongside it, since it is the same per-collector
behaviour for the same reason.
---
 .../collector-setup/kubernetes-helm-setup.md  | 45 ++++++++++++++++---
 1 file changed, 39 insertions(+), 6 deletions(-)

diff --git a/docs/instrument/collector-setup/kubernetes-helm-setup.md b/docs/instrument/collector-setup/kubernetes-helm-setup.md
index a2ed36c..a705a6d 100644
--- a/docs/instrument/collector-setup/kubernetes-helm-setup.md
+++ b/docs/instrument/collector-setup/kubernetes-helm-setup.md
@@ -106,13 +106,46 @@ scout:
     enabled: true
 ```
 
-The Windows daemon shares your Scout endpoint and credentials with the other
-collectors, so there is nothing further to configure.
+That is all you need if you let the chart generate your collector
+configuration.
 
-The exception is `extraEnvs`, which is per-collector: Helm replaces lists rather
-than merging them. If you supply the Scout secret through an environment
-variable rather than setting `scout.apiKey`, add the same entry under
-`windowsDaemon.extraEnvs` as well as `agent-collector.extraEnvs`.
+### If you supply your own collector configuration
+
+If you set `scout.agent.config` or `scout.daemon.config` — as the
+[otelcol style configuration](#using-otelcol-style-configuration) below does —
+you must supply `scout.windowsDaemon.config` too. The chart cannot generate one
+for you: your configuration carries its own credentials, under value names you
+chose, and a generated configuration would use different ones. Rather than
+authenticate the Windows daemon differently from every other collector, the
+chart refuses to render and tells you so.
+
+Use the same shape as your agent configuration, with Windows receivers:
+
+```yaml showLineNumbers title="values.yaml"
+scout:
+  windowsDaemon:
+    enabled: true
+    config: |
+      extensions:
+        oauth2client:
+          client_id: {{ .Values.scout.clientId }}
+          client_secret: {{ .Values.scout.clientSecret }}
+          token_url: {{ .Values.scout.tokenUrl }}
+      receivers:
+        filelog:
+          include:
+            - 'C:\var\log\pods\*\*\*.log'
+          start_at: end
+          operators:
+            - type: container
+              id: container-parser
+      # ...exporters, processors and pipelines as in your agent configuration
+```
+
+`extraEnvs` behaves the same way: it is per-collector, and Helm replaces lists
+rather than merging them. If you supply the Scout secret through an environment
+variable, add the same entry under `windowsDaemon.extraEnvs` as well as
+`agent-collector.extraEnvs`.
 
 ### What it collects
 

From 3ddd75ce31a35be1debde30da5c6b3e535388bbe Mon Sep 17 00:00:00 2001
From: thilak <thilak@base14.io>
Date: Thu, 24 Sep 2026 14:36:51 +0530
Subject: [PATCH 2/2] Bump the documented chart to 0.6.1

The page pinned 0.6.0, which is the version that silently falls back to a
generated Windows configuration when you supply your own for the other
collectors -- authenticating the Windows daemon with different credentials and
failing every export at runtime.

Documenting the requirement while still installing the version that does not
enforce it would be the worst of both: a reader who missed the new section
would hit exactly the failure it warns about.

0.6.1 refuses to render in that case instead.
---
 docs/instrument/collector-setup/kubernetes-helm-setup.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/instrument/collector-setup/kubernetes-helm-setup.md b/docs/instrument/collector-setup/kubernetes-helm-setup.md
index a705a6d..fdcf858 100644
--- a/docs/instrument/collector-setup/kubernetes-helm-setup.md
+++ b/docs/instrument/collector-setup/kubernetes-helm-setup.md
@@ -59,7 +59,7 @@ helm repo add base14 https://charts.base14.io/
 ```
 
 ```bash
-helm install scout base14/scout-collector --version 0.6.0 \
+helm install scout base14/scout-collector --version 0.6.1 \
 --namespace scout --create-namespace -f values.yaml
 ```
 
@@ -73,7 +73,7 @@ helm repo add base14 https://charts.base14.io/
 ```
 
 ```bash
-helm install scout base14/scout-collector --version 0.6.0 \
+helm install scout base14/scout-collector --version 0.6.1 \
 --namespace scout --create-namespace -f values.yaml
 ```