Requesting CRI-O and Kubelet profiling data by using the Node Observability Operator

The following workflow outlines on how to query the profiling data using the Node Observability Operator:

1. Install the Node Observability Operator in the OKD cluster.

2. Create a NodeObservability custom resource to enable the CRI-O profiling on the worker nodes of your choice.

3. Run the profiling query to generate the profiling data.

The Node Observability Operator is not installed in OKD by default. You can install the Node Observability Operator by using the OKD CLI or the web console.

You can install the Node Observability Operator by using the OpenShift CLI (oc).

Prerequisites

• You have installed the OpenShift CLI (oc).

• You have access to the cluster with privileges.

Procedure

1. Confirm that the Node Observability Operator is available by running the following command:

   Example output

   NAME                            CATALOG                AGE
   node-observability-operator     Red Hat Operators      9h

2. Create the node-observability-operator namespace by running the following command:

   $ oc new-project node-observability-operator

3. Create an OperatorGroup object YAML file:

   cat <<EOF | oc apply -f -
   apiVersion: operators.coreos.com/v1
   kind: OperatorGroup
   metadata:
     name: node-observability-operator
     namespace: node-observability-operator
   spec:
     targetNamespaces: []
   EOF

4. Create a Subscription object YAML file to subscribe a namespace to an Operator:

   cat <<EOF | oc apply -f -
   apiVersion: operators.coreos.com/v1alpha1
   kind: Subscription
   metadata:
     name: node-observability-operator
     namespace: node-observability-operator
   spec:
     channel: alpha
     name: node-observability-operator
     source: redhat-operators
   EOF

Verification

1. View the install plan name by running the following command:

   $ oc -n node-observability-operator get sub node-observability-operator -o yaml | yq '.status.installplan.name'

   Example output

   install-dt54w

2. Verify the install plan status by running the following command:

   <install_plan_name> is the install plan name that you obtained from the output of the previous command.

   Example output

   COMPLETE

3. $ oc get deploy -n node-observability-operator

   Example output

   NAME                                            READY   UP-TO-DATE  AVAILABLE   AGE
   

Installing the Node Observability Operator using the web console

You can install the Node Observability Operator from the OKD web console.

Prerequisites

• You have access to the cluster with cluster-admin privileges.

• You have access to the OKD web console.

Procedure

1. Log in to the OKD web console.

2. In the Administrator’s navigation panel, expand Operators → OperatorHub.

3. In the All items field, enter Node Observability Operator and select the Node Observability Operator tile.

4. Click Install.

5. On the Install Operator page, configure the following settings:

   1. In the Update channel area, click alpha.

   2. In the Installation mode area, click A specific namespace on the cluster.

   3. From the Installed Namespace list, select node-observability-operator from the list.

   4. In the Update approval area, select Automatic.

   5. Click Install.

Verification

1. In the Administrator’s navigation panel, expand Operators → Installed Operators.

2. Verify that the Node Observability Operator is listed in the Operators list.

You must create and run the NodeObservability custom resource (CR) before you run the profiling query. When you run the NodeObservability CR, it creates the necessary machine config and machine config pool CRs to enable the CRI-O profiling on the worker nodes matching the nodeSelector.

The CRI-O unix socket of the node is mounted on the agent pod, which allows the agent to communicate with CRI-O to run the pprof request. Similarly, the kubelet-serving-ca certificate chain is mounted on the agent pod, which allows secure communication between the agent and node’s kubelet endpoint.

• You have installed the Node Observability Operator.

• You have installed the OpenShift CLI (oc).

• You have access to the cluster with cluster-admin privileges.

Procedure

1. Log in to the OKD CLI by running the following command:

   $ oc login -u kubeadmin https://<HOSTNAME>:6443

2. Switch back to the node-observability-operator namespace by running the following command:

   $ oc project node-observability-operator

3. Create a CR file named nodeobservability.yaml that contains the following text:

       apiVersion: nodeobservability.olm.openshift.io/v1alpha2
       kind: NodeObservability
       metadata:
         name: cluster (1)
       spec:
           kubernetes.io/hostname: <node_hostname> (2)
         type: crio-kubelet

4. Run the NodeObservability CR:

   Example output

   nodeobservability.olm.openshift.io/cluster created

5. Review the status of the NodeObservability CR by running the following command:

   $ oc get nob/cluster -o yaml | yq '.status.conditions'

   Example output

   conditions:
     conditions:
     - lastTransitionTime: "2022-07-05T07:33:54Z"
       message: 'DaemonSet node-observability-ds ready: true NodeObservabilityMachineConfig
         ready: true'
       reason: Ready
       type: Ready

   NodeObservability CR run is completed when the reason is Ready and the status is True.

To run the profiling query, you must create a NodeObservabilityRun resource. The profiling query is a blocking operation that fetches CRI-O and Kubelet profiling data for a duration of 30 seconds. After the profiling query is complete, you must retrieve the profiling data inside the container file system /run/node-observability directory. The lifetime of data is bound to the agent pod through the emptyDir volume, so you can access the profiling data while the agent pod is in the running status.

Prerequisites

• You have installed the Node Observability Operator.

• You have created the NodeObservability custom resource (CR).

• You have access to the cluster with cluster-admin privileges.

Procedure

1. Create a NodeObservabilityRun resource file named nodeobservabilityrun.yaml that contains the following text:

   apiVersion: nodeobservability.olm.openshift.io/v1alpha2
   kind: NodeObservabilityRun
   metadata:
     name: nodeobservabilityrun
   spec:
     nodeObservabilityRef:
       name: cluster

2. Trigger the profiling query by running the NodeObservabilityRun resource:

   $ oc apply -f nodeobservabilityrun.yaml

3. Review the status of the NodeObservabilityRun by running the following command:

   $ oc get nodeobservabilityrun nodeobservabilityrun -o yaml  | yq '.status.conditions'

   Example output

4. Retrieve the profiling data from the container’s /run/node-observability path by running the following bash script:

   for a in $(oc get nodeobservabilityrun nodeobservabilityrun -o yaml | yq .status.agents[].name); do
     echo "agent ${a}"
     mkdir -p "/tmp/${a}"
     for p in $(oc exec "${a}" -c node-observability-agent -- bash -c "ls /run/node-observability/*.pprof"); do
       f="$(basename ${p})"
       echo "copying ${f} to /tmp/${a}/${f}"
       oc exec "${a}" -c node-observability-agent -- cat "${p}" > "/tmp/${a}/${f}"
   done