CFE-473: Add information about profiling data lifetime

[xenolinux]

Version(s): 4.12+

Issue: https://issues.redhat.com/browse/CFE-473

Link to docs preview: http://file.rdu.redhat.com/sdudhgao/nob-data-profiling/scalability_and_performance/node-observability-operator.html#running-profiling-query_node-observability-operator

QE review:

• QE has approved this change.

Additional information:

[ocpdocs-previewbot]

🤖 Updated build preview is available at:
https://52213--docspreview.netlify.app

Build log: https://circleci.com/gh/ocpdocs-previewbot/openshift-docs/3093

[alebedev87]

Thanks for the PR, @xenolinux !

Just a small proposal. emptyDir change is just a little technical detail which doesn't change a lot for the end user. I think it doesn't really deserve to be at the very beginning of the NodeObservability Operator's page. I was thinking of Running the profiling query chapter more. This phrase can be a good candidate for mentioning emptyDir:

After the profiling query is complete, you must retrieve the profiling data inside the container file system /run/node-observability directory.

[alebedev87]

Suggested change

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 in the `emptyDir` volume. You can access the profiling data as long as a pod is in the `running` status.

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 data's life time is bound to the agent pod via the `emptyDir` volume, so you can access the profiling data as long as a pod is in the `running` status.

[xenolinux]

Addressed

[alebedev87]

/lgtm

[sunilcio]

/lgtm

[openshift-ci]

New changes are detected. LGTM label has been removed.

[xenolinux]

/label peer-review-needed

[abhatt-rh]

/label peer-review-in-progress

[abhatt-rh]

LGTM, except a minor comment!

/remove-label peer-review-in-progress
/remove-label peer-review-needed
/label peer-review-done

[abhatt-rh]

Refer to ISG > Word Usage for as long as

Suggested change

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 as long as the agent pod is in the `running` status.

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.

[xenolinux]

Addressed

[xenolinux]

/label merge-review-needed

[mjpytlak]

/cherrypick enterprise-4.12

[mjpytlak]

/cherrypick enterprise-4.12

[openshift-cherrypick-robot]

@mjpytlak: new pull request created: #52556

In response to this:

/cherrypick enterprise-4.12

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.