Overview
OneIQ Pulse supports telemetry for Kubernetes services, pods, clusters, nodes and persistent volumes.
Prerequisites
Kubernetes cluster version 1.19.11, or higher.
Connectivity to the following public repositories:
Storage class allowing the provisioning of a persistent volume for the OneIQ Pulse connector.
Outbound Internet connectivity via port 443 (SSL) to OneIQ.
Discovering a Kubernetes cluster
Login to the OneIQ Portal
Click IT Environments in the left navigation menu
Select an IT Environment, go to the Connectors tab and select Kubernetes
Specify the name of the OneIQ Pulse connector.
In the Download manifest section, define a namespace and optionally add tolerations, separated by spaces.
Click Download to generate a .1iq Kubernetes manifest, customized for the selected IT environment. It must be deployed within 24 hours before it expires.
Run the following command in the target Kubernetes cluster:
kubectl apply -f <name of the manifest>.1iq
To check the status of the OneIQ Pulse connector in the Kubernetes cluster, run the following command:
kubectl get pods -n oneiq
Repeat the steps above steps for each Kubernetes cluster.
Example
If you export the MyKubernetesCluster (My IT environment).1iq manifest and run the following command:
kubectl apply -f "MyKubernetesCluster (My IT environment).1iq"
The output should be:
kubectl apply -f "MyKubernetesCluster (My IT environment).1iq"
namespace/oneiq created
serviceaccount/oneiq-pulse-collector created
clusterrole.rbac.authorization.k8s.io/oneiq-pulse-collector-zqlbn created
clusterrolebinding.rbac.authorization.k8s.io/oneiq-pulse-collector-zqlbn 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
Here is sample output if you check the status of the OneIQ Pulse connector:
NAME READY STATUS RESTARTS AGE
oneiq-pulse-collector-d9fb7f9d7-mrvqm 1/1 Running 0 8m29s