Skip to content

Document Windows node support for the collector - #260

Merged
thilak009 merged 3 commits into
mainfrom
docs-windows-collector
Sep 24, 2026
Merged

thilak009 merged 3 commits into
mainfrom
docs-windows-collector

Conversation

@thilak009

Copy link
Copy Markdown
Contributor

Adds a Windows Nodes section to the Kubernetes install guide. Chart 0.6.0 can collect from Windows nodes, but nothing on this page said so or explained why it needs separate configuration.

What it covers

  • Why a second DaemonSet is required — one pod template carries one image, the collector image is published separately for Linux and Windows, and the Linux daemon mounts host paths Windows pods do not support
  • The opt-in, which is one line: scout.windowsDaemon.enabled: true
  • What is and is not collected — container logs and kubelet stats; not host metrics, Event Log or perf counters
  • Server 2019 tag override, and a note that mixed 2019/2022 clusters need one DaemonSet per build
  • Common options — tolerations, host log path, runAsUserName, resources

Two things called out because they are easy to get wrong

extraEnvs is per-collector, and Helm replaces lists rather than merging them. A deployment that injects the Scout secret via env var needs its own copy under windowsDaemon.extraEnvs; one that sets scout.apiKey directly needs nothing. Getting this wrong gives a pod stuck in CreateContainerConfigError or silently unauthenticated exports.

The agent Service is named after the Helm release. With the helm install scout ... command on this page that is scout-agent-collector, not scout-collector-agent-collector — which is what I first wrote, and which matches the endpoint already used further down the page at line 511.

Verification

Every snippet was rendered against the published 0.6.0 chart from charts.base14.io, not a local copy:

  • enabled: true alone renders the Windows resources and inherits auth from the existing scout.* values
  • the Server 2019 tag override produces the expected image
  • runAsUserName, tolerations and hostLogPath render together as documented
  • the agent Service name was confirmed against the release name this page instructs

Marked experimental: it is off by default and has not yet run on a live Windows node group.

🤖 Generated with Claude Code

Chart 0.6.0 can collect from Windows nodes, but nothing on this page said so or
explained why it needs separate configuration.

Adds a Windows Nodes section covering: why a second DaemonSet is required (one
pod template cannot carry both a Linux and a Windows image, and the Linux daemon
mounts host paths Windows pods do not support), the one-line opt-in, what is and
is not collected, the Server 2019 tag override, and the common options
(tolerations, host log path, runAsUserName, resources).

Two things it calls out because they are easy to get wrong:

- extraEnvs is per-collector and Helm replaces lists rather than merging, so a
  deployment that injects the Scout secret by env var needs its own copy under
  windowsDaemon.extraEnvs. Deployments that set scout.apiKey directly need
  nothing.
- the agent Service is named after the Helm release, so with the install command
  on this page it is scout-agent-collector, matching the endpoint already used
  further down the page.

Marked experimental: it is disabled by default and has not yet run on a live
Windows node group.
The install guide pins 0.6.0, so what older chart versions did with Linux
collectors on Windows nodes is not something a reader needs. Documentation
should describe how the thing works, not how it used to be broken -- that
belongs in release notes.

Also drops "new and" from the experimental note: the status is what matters
and it stays accurate, where novelty dates itself.
The Quick Start on the same page already installs --version 0.6.0, so repeating
a pinned helm upgrade here implied the reader was on an older release and had to
upgrade to get this. It is an install guide: enabling Windows is one more values
block, applied by the command already given.

Also drops the "the values.yaml you already use" framing for the same reason --
it assumed an existing deployment the page has not described.
@thilak009
thilak009 merged commit 0b04617 into main Sep 24, 2026
5 checks passed
@thilak009
thilak009 deleted the docs-windows-collector branch September 24, 2026 08:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant