Skip to content

Disable install telemetry

Turn off the anonymous install report that the Omnia operator sends every 24 hours.

  • An Omnia install managed with Helm, or the operator Deployment from the kustomize manifests.
  • Permission to upgrade the release or edit the operator Deployment.
  1. Set telemetry.enabled to false on the release:

    Terminal window
    helm upgrade omnia oci://ghcr.io/altairalabs/charts/omnia \
    --devel \
    --reuse-values \
    --set telemetry.enabled=false

    The chart renders the value as OMNIA_TELEMETRY_ENABLED on the operator Deployment.

  2. If you install with kustomize or raw manifests, set OMNIA_TELEMETRY_ENABLED=false on 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 as flase.

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.

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:

Terminal window
kubectl exec -n omnia-system \
deploy/omnia-controller-manager -- /manager --print-telemetry

The 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.