$ oc -n openshift-monitoring edit configmap cluster-monitoring-config
- Documentation
- OpenShift Container Platform
- Telemetry
- Opting out of Telemetry history
OpenShift docs are moving and will soon only be available at docs.redhat.com, the home of all Red Hat product documentation. Explore the new docs experience today.
- About
- Release notes
- Architecture
- Installing
- Updating clusters
- Support
- Web console
- Authentication
- Understanding authentication
- Configuring the internal OAuth server
- Understanding identity provider configuration
- Configuring identity providers
- Configuring an HTPasswd identity provider
- Configuring a Keystone identity provider
- Configuring an LDAP identity provider
- Configuring a basic authentication identity provider
- Configuring a request header identity provider
- Configuring a GitHub or GitHub Enterprise identity provider
- Configuring a GitLab identity provider
- Configuring a Google identity provider
- Configuring an OpenID Connect identity provider
- Configuring certificates
- Using RBAC to define and apply permissions
- Removing the kubeadmin user
- Configuring the user agent
- Understanding and creating service accounts
- Using service accounts in applications
- Using a service account as an OAuth client
- Scoping tokens
- Managing Security Context Constraints
- Impersonating the system:admin user
- Syncing LDAP groups
- Networking
- Storage
- Understanding persistent storage
- Configuring persistent storage
- Persistent storage using AWS Elastic Block Store
- Persistent storage using Fibre Channel
- Persistent storage using NFS
- Persistent storage using hostPath
- Persistent Storage using iSCSI
- Persistent storage using Container Storage Interface (CSI)
- Persistent storage using VMware vSphere
- Persistent storage using volume snapshots
- Expanding persistent volumes
- Dynamic provisioning
- Registry
- Builds
- Understanding image builds
- Understanding build configurations
- Creating build inputs
- Managing build output
- Using build strategies
- Custom image builds with Buildah
- Performing basic builds
- Triggering and modifying builds
- Performing advanced builds
- Using Red Hat subscriptions in builds
- Securing builds by strategy
- Build configuration resources
- Troubleshooting builds
- Setting up additional trusted certificate authorities for builds
- Images
- Applications
- Machine management
- Nodes
- Working with pods
- Controlling pod placement onto nodes (scheduling)
- About pod placement using the scheduler
- Configuring the default scheduler to control pod placement
- Placing pods relative to other pods using pod affinity and anti-affinity rules
- Controlling pod placement on nodes using node affinity rules
- Placing pods onto overcommited nodes
- Controlling pod placement using node taints
- Placing pods on specific nodes using node selectors
- Using Jobs and DaemonSets
- Working with nodes
- Working with containers
- Using containers
- Using Init Containers to perform tasks before a pod is deployed
- Using volumes to persist container data
- Mapping volumes using projected volumes
- Allowing containers to consume API objects
- Copying files to or from a container
- Executing remote commands in a container
- Using port forwarding to access applications in a container
- Working with clusters
- Logging
- About cluster logging
- About deploying cluster logging
- Deploying cluster logging
- Viewing the Kibana interface
- Deploying and Configuring the Event Router
- Configuring your cluster logging deployment
- Viewing Elasticsearch status
- Moving the cluster logging resources with node selectors
- Manually rolling out Elasticsearch
- Troubleshooting Kibana
- Exported fields
- Uninstalling cluster logging
- Monitoring
- Telemetry
- Scalability and performance
- Backup and restore
- CLI reference
- Service Mesh
- Serverless applications
- Getting started with OpenShift Serverless
- OpenShift Serverless product architecture
- Installing OpenShift Serverless
- Getting started with Knative services
- Monitoring OpenShift Serverless components
- Cluster logging with OpenShift Serverless
- Configuring Knative Serving autoscaling
- Using Knative Client
- Release Notes
×
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.
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.
Disabling Telemetry
You can disable Telemetry.
Procedure
-
Start editing the
cluster-monitoring-configConfigMap: -
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