Bump the documented scout-collector chart to 0.6.0 - #259
Merged
Merged
Conversation
The install guide pinned 0.5.5, which predates the kubernetes.io/os nodeSelector on the collectors. Every version available on charts.base14.io lacked that guard until today, so a customer adding a Windows node group to a cluster running scout-collector got the Linux collectors scheduled onto it, where they cannot start: the image manifest list is Linux-only, and the daemon mounts host paths with mountPropagation, which Windows pods do not support. 0.6.0 carries the guard, and adds opt-in Windows node support behind scout.windowsDaemon.enabled (default false, so this changes nothing for anyone who does not ask for it). 0.5.10 and 0.5.11 were mirrored to charts.base14.io at the same time, so the repo is no longer three versions behind charts.b14.dev. Verified against the live repo: helm pull --version 0.6.0 resolves, and rendering this page's own values.yaml example against it produces the expected resources with the OS guard present and no Windows resources.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps the documented
scout-collectorchart version from 0.5.5 to 0.6.0 — two lines in the Kubernetes install guide, one for each of the Fargate and Managed Nodes variants.Why
0.5.5 predates the
kubernetes.io/os: linuxnodeSelector on the collectors, and until today every version available oncharts.base14.iolacked that guard. A customer adding a Windows node group to a cluster already running scout-collector got the Linux collectors scheduled onto it, where they cannot start — the collector image's manifest list is Linux-only, and the daemon mounts host paths withmountPropagation, which Windows pods do not support at all.0.6.0 carries the guard, and adds opt-in Windows node support behind
scout.windowsDaemon.enabled, defaultfalse— so nothing changes for anyone who does not ask for it.Availability
This was blocked until now:
charts.base14.iois a manual mirror and had been sitting at 0.5.9. 0.5.10, 0.5.11 and 0.6.0 were mirrored today, so the repo is no longer three versions behindcharts.b14.dev.Verification
Against the live repo, not a local chart:
helm pull base14/scout-collector --version 0.6.0resolveswindowsDaemonblock, the OS guard, and image0.130.1values.yamlexample against it produces 7 resources, with the Linux guard present and zero Windows resourcesNote
0.6.0 also moves the chart's default collector image from
0.118.0to0.130.1, because the config the chart generates is rejected by 0.118.0 (oauth2client'sexpiry_bufferis not a valid key there). Anyone installing on chart defaults — which is what this guide tells them to do — was getting a collector that could not start.🤖 Generated with Claude Code