fix(telemetry): make the documented opt-out cover both collectors - #3791
Conversation
Telemetry is reported by two components, cozystack-operator (cluster facts) and cozystack-controller (application counts), but only the operator had a reachable switch. The documented opt-out sets cozystackOperator.disableTelemetry on the cozy-installer chart, which cannot reach a package the platform deploys, so cozystack-controller kept reporting after an operator had followed the procedure — silently, with nothing to indicate the opt-out was partial. The platform now exposes telemetry.disabled and threads it into the cozystack-controller component of the cozystack-engine Package, the same way the bundle already threads cilium, multus and linstor values. The installer key is also declared in values.yaml: it was only ever referenced from the template, so the documented --set target did not appear in the chart's own values. Both keys stay false by default; this changes no behaviour for anyone who has not opted out. Assisted-By: Claude Signed-off-by: Andrei Kvapil <kvapss@gmail.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (4)
📝 WalkthroughWalkthroughThe change adds separate platform and operator telemetry settings. The system bundle propagates platform telemetry opt-out to ChangesTelemetry opt-out
Estimated code review effort: 2 (Simple) | ~10 minutes Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Created backport PR for
Please cherry-pick the changes locally and resolve any conflicts. git fetch origin backport-3791-to-release-1.6
git worktree add --checkout .worktree/backport-3791-to-release-1.6 backport-3791-to-release-1.6
cd .worktree/backport-3791-to-release-1.6
git reset --hard HEAD^
git cherry-pick -x c3cead8f6455ea9d98804ed6902c260f6c25c744
git push --force-with-lease |
|
Created backport PR for
Please cherry-pick the changes locally and resolve any conflicts. git fetch origin backport-3791-to-release-1.5
git worktree add --checkout .worktree/backport-3791-to-release-1.5 backport-3791-to-release-1.5
cd .worktree/backport-3791-to-release-1.5
git reset --hard HEAD^
git cherry-pick -x c3cead8f6455ea9d98804ed6902c260f6c25c744
git push --force-with-lease |
What this PR does
Telemetry is reported by two components —
cozystack-operator(cluster facts) andcozystack-controller(application counts) — but only the operator had a reachable switch.The documented opt-out sets
cozystackOperator.disableTelemetryon thecozy-installerchart. That chart deploys the operator; it cannot reach a package the platform deploys.packages/system/cozystack-controllerhas its own independentdisableTelemetrykey that nothing propagated to, so after an operator had followed the published procedure the controller kept postingcozy_application_countevery 15 minutes. Nothing failed, and nothing indicated the opt-out was partial.Two changes:
packages/core/platformgains atelemetry.disabledkey and threads it into thecozystack-controllercomponent of thecozystack.cozystack-enginePackage — the same mechanism the bundle already uses for cilium, multus and linstor values.packages/core/installer/values.yamldeclarescozystackOperator.disableTelemetry. It was only ever referenced from the template, so the--settarget the documentation names did not appear in the chart's own values.Both keys default to
false. Nobody who has not opted out sees a behaviour change.The opt-out remains two steps, because the two collectors are installed by two different charts. Collapsing it into one knob would mean the operator writing the value into the platform Package it does not own, which is a design change rather than a fix.
helm unitteston the platform chart: 137 passed (133 before, plus the four added here).helm lintclean on both charts.Screenshots
Not a UI change.
Downstream repositories
Trigger map walked against the diff.
packages/core/platform/values.yamlchanged, which the map routes to the website's hand-written platform-package table; the same change also makes the published opt-out procedure wrong, so the docs follow-up covers both.Release note
Summary by CodeRabbit
New Features
Bug Fixes