OneIQ

OneIQ Pulse supports telemetry for RedHat OpenShift services, pods, clusters, nodes, and persistent volumes.

Red Hat OpenShift Platform version 4 or higher.

Connectivity to the following public repositories: 

- <a href="http://mcr.microsoft.com/dotnet/" rel="nofollow noopener noreferrer" target="_blank">http://mcr.microsoft.com/dotnet/</a>
- <a href="http://oneiqpub.azurecr.io" rel="nofollow noopener noreferrer" target="_blank">http://oneiqpub.azurecr.io</a>

Storage class allowing the provisioning of a persistent volume for the OneIQ Pulse connector. 

Outbound Internet connectivity via port 443 (SSL) to OneIQ.

- Red Hat OpenShift Platform version 4 or higher.
- Connectivity to the following public repositories: 
 - <a href="http://mcr.microsoft.com/dotnet/" rel="nofollow noopener noreferrer" target="_blank">http://mcr.microsoft.com/dotnet/</a>
 - <a href="http://oneiqpub.azurecr.io" rel="nofollow noopener noreferrer" target="_blank">http://oneiqpub.azurecr.io</a>
- Storage class allowing the provisioning of a persistent volume for the OneIQ Pulse connector. 
- Outbound Internet connectivity via port 443 (SSL) to OneIQ.

Login to the <a href="https://my.oneiq.com" rel="nofollow noopener noreferrer" target="_blank">OneIQ Portal</a>

Click <a href="https://my.oneiq.com/environments" rel="nofollow noopener noreferrer" target="_blank">IT Environments</a> in the left navigation menu

Select an IT environment, go to the Connectors tab, and select OpenShift ​

Specify the name for the OneIQ Pulse connector.

In the Download Manifest section, define a namespace and optionally add <a href="https://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/" rel="nofollow noopener noreferrer" target="_blank">tolerations</a> separated by spaces. ​

Click Download to generate a .1iq manifest for Red Hat OpenShift customized for the selected IT environment. The manifest must be deployed within 24 hours before it expires. ​

Run the following command in the target cluster using the Red Hat OpenShift command-line interface:

oc apply -f &lt;the name of the manifest).1iq

Repeat the steps above steps for each Red Hat OpenShift cluster.

1. Login to the <a href="https://my.oneiq.com" rel="nofollow noopener noreferrer" target="_blank">OneIQ Portal</a>
2. Click <a href="https://my.oneiq.com/environments" rel="nofollow noopener noreferrer" target="_blank">IT Environments</a> in the left navigation menu
3. Select an IT environment, go to the Connectors tab, and select OpenShift ​
 
 
4. Specify the name for the OneIQ Pulse connector.
5. In the Download Manifest section, define a namespace and optionally add <a href="https://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/" rel="nofollow noopener noreferrer" target="_blank">tolerations</a> separated by spaces. ​ 
 
 
6. Click Download to generate a .1iq manifest for Red Hat OpenShift customized for the selected IT environment. The manifest must be deployed within 24 hours before it expires. ​
 
 
7. Run the following command in the target cluster using the Red Hat OpenShift command-line interface:
 oc apply -f &lt;the name of the manifest).1iq
 
 Repeat the steps above steps for each Red Hat OpenShift cluster.

If you export the MyOpenShiftCluster (My IT environment).1iq manifest and run the following command:

oc apply -f "MyOpenShiftCluster (My IT environment).1iq"

namespace/oneiq created serviceaccount/oneiq-pulse-collector created clusterrole.rbac.authorization.k8s.io/oneiq-pulse-collector-w6dj4 created clusterrolebinding.rbac.authorization.k8s.io/oneiq-pulse-collector-w6dj4 created role.rbac.authorization.k8s.io/oneiq-pulse-collector created rolebinding.rbac.authorization.k8s.io/oneiq-pulse-collector created persistentvolumeclaim/oneiq-pulse-pv created deployment.apps/oneiq-pulse-collector created

Learn how to use the OneIQ Pulse connector to profile Red Hat OpenShift clusters.

Overview

Prerequisites

Discovering an OpenShift cluster

Example