From b6381cc35f0983310344e7acb064ea3262fb580d Mon Sep 17 00:00:00 2001 From: Andrei Kvapil Date: Wed, 12 Aug 2026 19:49:58 +0200 Subject: [PATCH 1/2] fix(telemetry): document the opt-out for both collectors The page names two telemetry collectors, cozystack-operator and cozystack-controller, and then gave a single opt-out that only reaches the operator. cozystack-controller is deployed by the platform, not by the cozy-installer chart, so it kept reporting application counts after a reader had followed the documented procedure. Both steps are now given. On next, the second step uses the platform's new telemetry.disabled key; on v1.6, which has no such key, it overrides the component values directly. Assisted-By: Claude Signed-off-by: Andrei Kvapil --- .../operations/configuration/telemetry.md | 25 ++++++++++++++++-- .../operations/configuration/telemetry.md | 26 +++++++++++++++++-- 2 files changed, 47 insertions(+), 4 deletions(-) diff --git a/content/en/docs/next/operations/configuration/telemetry.md b/content/en/docs/next/operations/configuration/telemetry.md index 845730d6..1dfd8ed2 100644 --- a/content/en/docs/next/operations/configuration/telemetry.md +++ b/content/en/docs/next/operations/configuration/telemetry.md @@ -66,7 +66,11 @@ We respect your privacy and choice regarding telemetry. If you prefer not to par Opting Out: -To disable telemetry reporting, upgrade the Cozystack operator Helm release with the `disableTelemetry` flag: +Telemetry is sent by the two components named above, and they are installed by +two different charts, so opting out takes two steps. Doing only the first +leaves `cozystack-controller` reporting application counts. + +**1. The operator**, which is part of the `cozy-installer` release: ```bash helm upgrade cozystack oci://ghcr.io/cozystack/cozystack/cozy-installer \ @@ -79,7 +83,24 @@ Replace `X.Y.Z` with your currently installed Cozystack version. {{< reuse-values-warning >}} -This command updates the operator to disable telemetry data collection. If you wish to re-enable telemetry in the future, run the same command with `disableTelemetry=false`. +**2. The controller**, which the platform deploys. Set `telemetry.disabled` in +the Platform Package and apply it: + +```yaml +apiVersion: cozystack.io/v1alpha1 +kind: Package +metadata: + name: cozystack.cozystack-platform +spec: + components: + platform: + values: + telemetry: + disabled: true +``` + +To re-enable telemetry later, run the same command with +`disableTelemetry=false` and set `telemetry.disabled: false`. ## Conclusion diff --git a/content/en/docs/v1.6/operations/configuration/telemetry.md b/content/en/docs/v1.6/operations/configuration/telemetry.md index 04597a00..d2fdd87a 100644 --- a/content/en/docs/v1.6/operations/configuration/telemetry.md +++ b/content/en/docs/v1.6/operations/configuration/telemetry.md @@ -66,7 +66,11 @@ We respect your privacy and choice regarding telemetry. If you prefer not to par Opting Out: -To disable telemetry reporting, upgrade the Cozystack operator Helm release with the `disableTelemetry` flag: +Telemetry is sent by the two components named above, and they are installed by +two different charts, so opting out takes two steps. Doing only the first +leaves `cozystack-controller` reporting application counts. + +**1. The operator**, which is part of the `cozy-installer` release: ```bash helm upgrade cozystack oci://ghcr.io/cozystack/cozystack/cozy-installer \ @@ -79,7 +83,25 @@ Replace `X.Y.Z` with your currently installed Cozystack version. {{< reuse-values-warning >}} -This command updates the operator to disable telemetry data collection. If you wish to re-enable telemetry in the future, run the same command with `disableTelemetry=false`. +**2. The controller**, which the platform deploys. This version has no +platform-level key for it, so override the component's values directly on the +`cozystack.cozystack-engine` Package: + +```yaml +apiVersion: cozystack.io/v1alpha1 +kind: Package +metadata: + name: cozystack.cozystack-engine +spec: + components: + cozystack-controller: + values: + cozystackController: + disableTelemetry: true +``` + +To re-enable telemetry later, run the same command with +`disableTelemetry=false` and set `disableTelemetry: false` on the component. ## Conclusion From 254b0e3e0690b83bbf798fb102a80634fa9c4afc Mon Sep 17 00:00:00 2001 From: Andrei Kvapil Date: Wed, 12 Aug 2026 22:56:48 +0200 Subject: [PATCH 2/2] fix(telemetry): document the controller opt-out for v1.5 too v1.5 is still installed and carries the same incomplete instruction. It gets the v1.6 form, which overrides the component values directly, since neither version has the platform-level telemetry.disabled key. Earlier documentation versions are left alone. Assisted-By: Claude Signed-off-by: Andrei Kvapil --- .../operations/configuration/telemetry.md | 26 +++++++++++++++++-- 1 file changed, 24 insertions(+), 2 deletions(-) diff --git a/content/en/docs/v1.5/operations/configuration/telemetry.md b/content/en/docs/v1.5/operations/configuration/telemetry.md index dfdfe0fc..52c1c7c4 100644 --- a/content/en/docs/v1.5/operations/configuration/telemetry.md +++ b/content/en/docs/v1.5/operations/configuration/telemetry.md @@ -66,7 +66,11 @@ We respect your privacy and choice regarding telemetry. If you prefer not to par Opting Out: -To disable telemetry reporting, upgrade the Cozystack operator Helm release with the `disableTelemetry` flag: +Telemetry is sent by the two components named above, and they are installed by +two different charts, so opting out takes two steps. Doing only the first +leaves `cozystack-controller` reporting application counts. + +**1. The operator**, which is part of the `cozy-installer` release: ```bash helm upgrade cozystack oci://ghcr.io/cozystack/cozystack/cozy-installer \ @@ -79,7 +83,25 @@ Replace `X.Y.Z` with your currently installed Cozystack version. {{< reuse-values-warning >}} -This command updates the operator to disable telemetry data collection. If you wish to re-enable telemetry in the future, run the same command with `disableTelemetry=false`. +**2. The controller**, which the platform deploys. This version has no +platform-level key for it, so override the component's values directly on the +`cozystack.cozystack-engine` Package: + +```yaml +apiVersion: cozystack.io/v1alpha1 +kind: Package +metadata: + name: cozystack.cozystack-engine +spec: + components: + cozystack-controller: + values: + cozystackController: + disableTelemetry: true +``` + +To re-enable telemetry later, run the same command with +`disableTelemetry=false` and set `disableTelemetry: false` on the component. ## Conclusion