|
| 1 | +// Module included in the following assemblies: |
| 2 | +// |
| 3 | +// * support/remote_health_monitoring/using-insights-operator.adoc |
| 4 | + |
| 5 | + |
| 6 | +:_content-type: PROCEDURE |
| 7 | +[id="insights-operator-configuring-sca_{context}"] |
| 8 | += Configuring Insights Operator |
| 9 | + |
| 10 | +You can configure Insights Operator to meet the needs of your organization. The Insights Operator is configured using a combination of the default configurations in the `pod.yaml` file in the Insights Operator `Config` directory and the configurations stored in the `support` secret in the `openshift-config` namespace. The `support` secret does not exist by default and must be created when adding custom configurations for the first time. Configurations in the `support` secret override the defaults set in the `pod.yaml` file. |
| 11 | + |
| 12 | +The table below describes the available configuration attributes: |
| 13 | + |
| 14 | +.Insights Operator configurable attributes |
| 15 | +[options="header"] |
| 16 | +|==== |
| 17 | +|Attribute name|Description|Value type|Default value |
| 18 | +|`username`|Specifies username for basic authentication with `console.redhat.com` (overrides the default `pull-secret` token authentication when set)|String|Not set |
| 19 | +|`password`|Specifies password for basic authentication with `console.redhat.com` (overrides the default `pull-secret` token authentication when set)|String|Not set |
| 20 | +|`enableGlobalObfuscation`|Enables the global obfuscation of IP addresses and the cluster domain name|Boolean|`false` |
| 21 | +|`scaInterval`|Specifies the frequency of the simple content access entitlements download|Time interval|`8h` |
| 22 | +|`scaPullDisabled`|Disables the simple content access entitlements download|Boolean|`false` |
| 23 | +|`clusterTransferInterval`|Specifies how often Insights Operator checks OpenShift Cluster Manager for available cluster transfers|Time interval|`24h` |
| 24 | +|`disableInsightsAlerts`|Disables Insights Operator alerts to the cluster Prometheus instance|Boolean|`False` |
| 25 | +|==== |
| 26 | + |
| 27 | +This procedure describes how to set custom Insights Operator configurations. |
| 28 | + |
| 29 | +[IMPORTANT] |
| 30 | +==== |
| 31 | +Red Hat recommends you consult Red Hat Support before making changes to the default Insights Operator configuration. |
| 32 | +==== |
| 33 | + |
| 34 | +.Prerequisites |
| 35 | + |
| 36 | +* You are logged in to the {product-title} web console as a user with `cluster-admin` role. |
| 37 | +
|
| 38 | +.Procedure |
| 39 | + |
| 40 | +. Navigate to *Workloads* -> *Secrets*. |
| 41 | +. On the *Secrets* page, select *All Projects* from the *Project* list, and then set *Show default projects* to on. |
| 42 | +. Select the *openshift-config* project from the *Project* list. |
| 43 | +. Search for the *support* secret using the *Search by name* field. If it does not exist, click *Create* -> *Key/value secret* to create it. |
| 44 | +. Click the *Options* menu {kebab} for the secret, and then click *Edit Secret*. |
| 45 | +. Click *Add Key/Value*. |
| 46 | +. Enter an attribute name with an appropriate value (see table above), and click *Save*. |
| 47 | +. Repeat the above steps for any additional configurations. |
0 commit comments