Opting out of remote health reporting

You may choose to opt out of reporting health and usage data for your cluster.

To opt out of remote health reporting, you must:

1. Modify the global cluster pull secret to disable remote health reporting.

2. Update the cluster to use this modified pull secret.

Consequences of disabling remote health reporting

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 monitor the success of product upgrades or the health of your clusters without a support case being opened.

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

In restricted networks, Telemetry and Insights data can still be reported through appropriate configuration of your proxy.

Modifying the global cluster pull secret to disable remote health reporting

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 cluster-admin role.

Procedure

1. Download the global cluster pull secret to your local file system.

   $ oc extract secret/pull-secret -n openshift-config --to=.

2. In a text editor, edit the .dockerconfigjson file that was downloaded.

3. Remove the cloud.openshift.com JSON entry, for example:

   "cloud.openshift.com":{"auth":"<hash>","email":"<email_address>"}

4. Save the file.

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

Registering your disconnected cluster

Register your disconnected OKD cluster on the Red Hat Hybrid Cloud Console so that your cluster is not impacted by the consequences listed in the section named “Consequences of disabling remote health reporting”.

Prerequisites

• You are logged in to the OKD web console as cluster-admin.

• You can log in to the Red Hat Hybrid Cloud Console.

Procedure

1. Go to the Register disconnected cluster web page on the Red Hat Hybrid Cloud Console.

2. Optional: To access the Register disconnected cluster web page from the home page of the Red Hat Hybrid Cloud Console, go to the Clusters navigation menu item and then select the Register cluster button.

3. Enter your cluster’s details in the provided fields on the Register disconnected cluster page.

4. From the Subscription settings section of the page, select the subcription settings that apply to your Red Hat subscription offering.

5. To register your disconnected cluster, select the Register cluster button.

Additional resources

• Consequences of disabling remote health reporting

• How does the subscriptions service show my subscription data?(Getting Started with the Subscription Service)

Updating the global cluster 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.

The procedure is required when users use a separate registry to store images than the registry used during installation.

Prerequisites

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

Procedure

1. 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:

      $ oc get secret/pull-secret -n openshift-config --template='{{index .data ".dockerconfigjson" | base64decode}}' ><pull_secret_location> (1)

      1	Provide the path to the pull secret file.

   2. Enter the following command to add the new pull secret:

      $ oc registry login --registry="<registry>" \ (1)
      --auth-basic="<username>:<password>" \ (2)
      --to=<pull_secret_location> (3)

      1	Provide the new registry. You can include multiple repositories within the same registry, for example: —registry=”<registry/my-namespace/my-repository>”.
      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.

2. Enter the following command to update the global pull secret for your cluster:

   $ oc set data secret/pull-secret -n openshift-config --from-file=.dockerconfigjson=<pull_secret_location> (1)

   1	Provide the path to the new pull secret file.

   This update is rolled out to all nodes, which can take some time depending on the size of your cluster.

   As of OKD 4.7.4, changes to the global pull secret no longer trigger a node drain or reboot.