Chapter 3. Opting out of Telemetry
You might need to opt out of Telemetry for your cluster. For example, you might need to comply with privacy laws.
Prerequisites
-
Install the OpenShift Command-line Interface (CLI), commonly known as
oc. -
You must log in to the cluster with a user that has the
cluster-adminrole. -
You need to have the
cluster-monitoring-configConfigMap object with thedata/config.yamlsection. See Creating cluster monitoring ConfigMap for details.
3.1. Consequences of disabling Telemetry
In OpenShift Container Platform 4.1, customers can opt out of the Telemetry service. However, Telemetry is embedded as a core component and serves as part of the overall function of the cluster. Therefore, opting out is strongly discouraged.
Some of the consequences of opting out of Telemetry are:
- The Red Hat OpenShift Cluster Manager does not work as expected and does not show critical information about your clusters.
-
You cannot perform subscription management, including legally entitling your purchase from Red Hat through
cloud.redhat.com. Because there is no disconnected subscription management, you cannot both opt out of sending data to Red Hat and entitle your purchase. - You will not gain quality assurance by reporting faults encountered during upgrades.
- You cannot entitle your cluster.
Deployment and management of OpenShift Container Platform for disconnected environments is a critical goal and will be delivered in a future version of OpenShift Container Platform.
3.2. Disabling Telemetry
You can disable Telemetry.
Procedure
Start editing the
cluster-monitoring-configConfigMap:$ oc -n openshift-monitoring edit configmap cluster-monitoring-config
Add the two lines that are required to disable Telemetry to the
data/config.yamlsection, as shown:apiVersion: v1 kind: ConfigMap metadata: name: cluster-monitoring-config namespace: openshift-monitoring data: config.yaml: |+ telemeterClient: enabled: false
