Opting out of remote health reporting

To opt out of remote health reporting, you must:

Modify the global cluster pull secret to disable remote health reporting.
to use this modified pull secret.

In OKD, customers can opt out of reporting usage information. However, connected clusters allow Red Hat to react more quickly to problems and better support our customers, as well as better understand how product upgrades impact clusters. Connected clusters also help to simplify the subscription and entitlement process and enable the OpenShift Cluster Manager service to provide an overview of your clusters and their subscription status.

Red Hat strongly recommends leaving health and usage reporting enabled for pre-production and test clusters even if it is necessary to opt out for production clusters. This allows Red Hat to be a participant in qualifying OKD in your environments and react more rapidly to product issues.

Some of the consequences of opting out of having a connected cluster are:

Red Hat will not be able to use configuration data to better triage customer support cases and identify which configurations our customers find important.
The OpenShift Cluster Manager will not show data about your clusters including health and usage information.

You can modify your existing global cluster pull secret to disable remote health reporting. This disables both Telemetry and the Insights Operator.

Prerequisites

You have access to the cluster as a user with the role.

Procedure

Download the global cluster pull secret to your local file system.
In a text editor, edit the file that was downloaded.
Save the file.

You can now update your cluster to use this modified pull secret.

You can update the global pull secret for your cluster by either replacing the current pull secret or appending a new pull secret.

Prerequisites

You have access to the cluster as a user with the role.

Procedure

Optional: To append a new pull secret to the existing pull secret, complete the following steps:
1. Enter the following command to download the pull secret:
2. Enter the following command to add the new pull secret:
  
  1 Provide the new registry. You can include multiple repositories within the same registry, for example: .
  2 Provide the credentials of the new registry.
  3 Provide the path to the pull secret file.
  
  Alternatively, you can perform a manual update to the pull secret file.

1	Provide the new registry. You can include multiple repositories within the same registry, for example: .
2	Provide the credentials of the new registry.
3	Provide the path to the pull secret file.