Andrei Kvapil c3cead8f64 fix(telemetry): make the documented opt-out cover both collectors ...

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>

2026-08-12 19:48:37 +02:00

..

example

[cozystack-operator] Add deployment files

2025-12-29 14:04:10 +01:00

images/cozystack-operator

chore(deps): update container image & action digests

2026-07-10 05:29:23 +00:00

templates

fix(installer): let the operator Deployment report Available honestly

2026-08-05 18:15:41 +03:00

tests

fix(installer): let the operator Deployment report Available honestly

2026-08-05 18:15:41 +03:00

.helmignore

refactor(installer): move CRDs to crds/ directory for proper Helm install ordering

2026-02-18 00:49:55 +03:00

Chart.yaml

Calculate tags and version automatically (#100)

2024-04-24 11:31:22 +02:00

Makefile

test(installer): cover COZYSTACK_VERSION env rendering

2026-07-06 10:03:48 +05:00

values.yaml

fix(telemetry): make the documented opt-out cover both collectors

2026-08-12 19:48:37 +02:00