From f27e4fa39d6da6472811dab9bcfecbe76a0f55cc Mon Sep 17 00:00:00 2001 From: Michelle Purcell Date: Thu, 20 Feb 2025 13:43:44 +0000 Subject: [PATCH] Add more content to the release notes about the Insights Operator in 4.18 Update release_notes/ocp-4-18-release-notes.adoc Co-authored-by: Jeana Routh <61474374+jeana-redhat@users.noreply.github.com> merge fix fix escape --- release_notes/ocp-4-18-release-notes.adoc | 39 +++++++++++++++++++++++ 1 file changed, 39 insertions(+) diff --git a/release_notes/ocp-4-18-release-notes.adoc b/release_notes/ocp-4-18-release-notes.adoc index 84d03b3dc0..dcd8c4fc05 100644 --- a/release_notes/ocp-4-18-release-notes.adoc +++ b/release_notes/ocp-4-18-release-notes.adoc @@ -524,6 +524,42 @@ Available as a Technology Preview, the Insights Runtime Extractor feature gather Red{nbsp}Hat uses the collected runtime workload data to gain insights that can help you make investment decisions that will drive and optimize how you use your {product-title} containers. For more information, see xref:../nodes/clusters/nodes-cluster-enabling-features.adoc#nodes-cluster-enabling[_Enabling features using feature gates_]. +[id="ocp-release-notes-insights-operator-rapid-recommendations_{context}"] +==== Rapid Recommendations + +In this release, enhancements have been made to the Rapid Recommendations mechanism for remotely configuring the rules that determine the data that the Insights Operator collects. + +The Rapid Recommendations feature is version-independent, and builds on the existing conditional data gathering mechanism. + + +The Insights Operator connects to a secure remote endpoint service running on _console.redhat.com_ to retrieve definitions that contain the rules for determining which container log messages are filtered and collected by Red{nbsp}Hat. + +The conditional data-gathering definitions get configured through an attribute named `conditionalGathererEndpoint` in the link:https://github.com/openshift/insights-operator/blob/master/config/pod.yaml[`pod.yml`] configuration file. + +[source,bash] +---- +conditionalGathererEndpoint: https://console.redhat.com/api/gathering/v2/%s/gathering_rules +---- + +[NOTE] +==== +In earlier iterations, the rules for determining the data that the Insights Operator collects were hard-coded and tied to the corresponding {product-title} version. +==== + +The preconfigured endpoint URL now provides a placeholder (`%s`) for defining a target version of {product-title}. + +[id="ocp-release-notes-insights-operator-more_data_collected_and_recommendations_added_{context}"] +==== More data collected and recommendations added + +The Insights Operator now gathers more data to detect the following scenarios, which other applications can use to generate remedial recommendations to proactively manage your {product-title} deployments: + +// Engineering reference: CCXDEV-14148 +* Collects resources from the `nmstate.io/v1` API group. + +// Engineering reference: CCXDEV-14521 +* Collects data from `clusterrole.rbac.authorization.k8s.io/v1` instances. + + [id="ocp-release-notes-installation-and-update_{context}"] === Installation and update @@ -1630,6 +1666,9 @@ If these values are not defined in a failure domain configuration, for instance [id="ocp-release-note-insights-operator-bug-fixes_{context}"] ==== Insights Operator +Previously, during entitled builds on a Red{nbsp}Hat {product-title} cluster running on {ibm-z-title} hardware, repositories were not enabled. This issue has been resolved. You can now enable repositories during entitled builds on a Red{nbsp}Hat {product-title} cluster running on {ibm-z-title} hardware. (OCPBUG-32233) + + [discrete] [id="ocp-release-note-kube-controller-bug-fixes_{context}"] ==== Kubernetes Controller Manager