operator: report host-tuner adoption in telemetry#1639
Open
david-yu wants to merge 1 commit into
Open
Conversation
Count Redpanda and StretchCluster resources with the opt-in chroot host tuners enabled (spec.tuning.apply_host_tuners) in the anonymous telemetry payload, as redpanda.hostTunersEnabled and stretchCluster.hostTunersEnabled. The counter reads the raw spec: apply_host_tuners is a pure opt-in (chart default false), so the explicit spec value is the effective state. The long-standing tune_aio_events tuner is deliberately excluded — this tracks adoption of the chroot host-tuner mode only. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
david-yu
requested review from
RafalKorepta,
andrewstucki,
chrisseto,
gene-redpanda and
hidalgopl
as code owners
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
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
2 participants
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.
Stacked on #1522 (requires the
apply_host_tunersCRD fields introduced there); retarget tomainonce #1522 merges.Adds host-tuner adoption to the operator's anonymous telemetry payload so we can see how many clusters have turned on the opt-in chroot tuning init container:
redpanda.hostTunersEnabled— count of Redpanda CRs withspec.tuning.apply_host_tuners: truestretchCluster.hostTunersEnabled— same count over StretchCluster CRsDesign notes:
apply_host_tunersis a pure opt-in (chart defaultfalse), so the explicit spec value is the effective state and no chart rendering is needed.tune_aio_eventstuner is deliberately not counted — it defaults on in the chart and would not signal host-tuner adoption. A dedicated test locks this semantic (aio-only and explicitapply_host_tuners: falseclusters do not count).Scope note: this telemetry is operator-side only. Pure
helm installdeployments (no operator) have no phone-home mechanism in the chart, so they are not captured by this signal.🤖 Generated with Claude Code