Disable install telemetry
Turn off the anonymous install report that the Omnia operator sends every 24 hours.
Prerequisites
Section titled “Prerequisites”- An Omnia install managed with Helm, or the operator Deployment from the kustomize manifests.
- Permission to upgrade the release or edit the operator Deployment.
-
Set
telemetry.enabledtofalseon the release:Terminal window helm upgrade omnia oci://ghcr.io/altairalabs/charts/omnia \--devel \--reuse-values \--set telemetry.enabled=falseThe chart renders the value as
OMNIA_TELEMETRY_ENABLEDon the operator Deployment. -
If you install with kustomize or raw manifests, set
OMNIA_TELEMETRY_ENABLED=falseon the operator container instead.An unset variable enables telemetry, and so does any value that parses as a Go boolean true (
true,1,t). Any other value disables it, including a typo such asflase.
The operator reads the variable once at startup, so the pod must restart. A Helm upgrade restarts it because the Deployment’s environment changes. No feature is gated on telemetry, so nothing else changes.
Verify
Section titled “Verify”Print the payload from the running operator. The first line on stderr reports the install’s state. The command assumes a release named omnia in the omnia-system namespace; adjust both to match yours:
kubectl exec -n omnia-system \ deploy/omnia-controller-manager -- /manager --print-telemetryThe status line begins telemetry status: DISABLED for this install. The JSON on stdout is a preview of what would be sent if you re-enabled telemetry. Nothing is sent.
Related pages
Section titled “Related pages”- Inspect the telemetry payload
- Install telemetry reference for every field and the transport
- Why telemetry is shaped the way it is