Merge pull request #351 from syedriko/syedriko-ols-1771

OLS-1771: Python deps and docs update, week of 2025/05/19

Author: openshift-merge-bot[bot]

ocp-product-docs-plaintext/4.15/hosted_control_planes/hcp-observability.txt

@@ -127,9 +127,9 @@ cvo:
 
 # Enabling monitoring dashboards in a hosted cluster
 
-To enable monitoring dashboards in a hosted cluster, complete the following steps:
+You can enable monitoring dashboards in a hosted cluster by creating a config map.
 
-1. Create the hypershift-operator-install-flags config map in the local-cluster namespace, being sure to specify the --monitoring-dashboards flag in the data.installFlagsToAdd section. For example:
+1. Create the hypershift-operator-install-flags config map in the local-cluster namespace. See the following example configuration:
 
 ```yaml
 kind: ConfigMap
@@ -138,10 +138,11 @@ metadata:
   name: hypershift-operator-install-flags
   namespace: local-cluster
 data:
-  installFlagsToAdd: "--monitoring-dashboards"
+  installFlagsToAdd: "--monitoring-dashboards --metrics-set=All" 1
   installFlagsToRemove: ""
 ```
 
+The --monitoring-dashboards --metrics-set=All flag adds the monitoring dashboard for all metrics.
 2. Wait a couple of minutes for the HyperShift Operator deployment in the hypershift namespace to be updated to include the following environment variable:
 
 ```yaml
@@ -152,7 +153,7 @@ data:
 
 When monitoring dashboards are enabled, for each hosted cluster that the HyperShift Operator manages, the Operator creates a config map named cp-<hosted_cluster_namespace>-<hosted_cluster_name> in the openshift-config-managed namespace, where <hosted_cluster_namespace> is the namespace of the hosted cluster and <hosted_cluster_name> is the name of the hosted cluster. As a result, a new dashboard is added in the administrative console of the management cluster.
 3. To view the dashboard, log in to the management cluster's console and go to the dashboard for the hosted cluster by clicking Observe -> Dashboards.
-4. Optional: To disable a monitoring dashboards in a hosted cluster, remove the --monitoring-dashboards flag from the hypershift-operator-install-flags config map. When you delete a hosted cluster, its corresponding dashboard is also deleted.
+4. Optional: To disable monitoring dashboards in a hosted cluster, remove the --monitoring-dashboards --metrics-set=All flag from the hypershift-operator-install-flags config map. When you delete a hosted cluster, its corresponding dashboard is also deleted.
 
 ## Dashboard customization
 

ocp-product-docs-plaintext/4.15/installing/installing_bare_metal_ipi/ipi-install-installation-workflow.txt

@@ -88,10 +88,10 @@ $ sudo firewall-cmd --zone=public --add-service=http --permanent
 $ sudo firewall-cmd --reload
 ```
 
-9. Start and enable the libvirtd service:
+9. Start the modular libvirt daemon sockets:
 
 ```terminal
-$ sudo systemctl enable libvirtd --now
+$ for drv in qemu interface network nodedev nwfilter secret storage; do sudo systemctl start virt${drv}d{,-ro,-admin}.socket; done
 ```
 
 10. Create the default storage pool and start it:

ocp-product-docs-plaintext/4.15/observability/logging/logging_release_notes/logging-5-8-release-notes.txt

@@ -12,6 +12,33 @@ Logging is provided as an installable component, with a distinct release cycle f
 The stable channel only provides updates to the most recent release of logging. To continue receiving updates for prior releases, you must change your subscription channel to stable-x.y, where x.y represents the major and minor version of logging you have installed. For example, stable-5.7.
 ----
 
+# Logging 5.8.20
+
+This release includes RHBA-2025:7450 and RHSA-2025:7451.
+
+## CVEs
+
+* CVE-2019-12900
+* CVE-2020-11023
+* CVE-2024-2236
+* CVE-2024-2511
+* CVE-2024-3596
+* CVE-2024-4603
+* CVE-2024-4741
+* CVE-2024-5535
+* CVE-2024-8176
+* CVE-2024-12133
+* CVE-2024-12243
+* CVE-2024-12797
+* CVE-2024-42292
+* CVE-2024-42322
+* CVE-2024-44990
+* CVE-2024-45338
+* CVE-2024-46826
+* CVE-2025-0395
+* CVE-2025-21927
+* CVE-2025-27363
+
 # Logging 5.8.19
 
 This release includes RHBA-2025:3447 and RHSA-2025:3448.

ocp-product-docs-plaintext/4.15/observability/logging/logging_release_notes/logging-5-9-release-notes.txt

@@ -8,6 +8,30 @@ Logging is provided as an installable component, with a distinct release cycle f
 The stable channel only provides updates to the most recent release of logging. To continue receiving updates for prior releases, you must change your subscription channel to stable-x.y, where x.y represents the major and minor version of logging you have installed. For example, stable-5.7.
 ----
 
+# Logging 5.9.14
+
+This release includes RHSA-2025:7449.
+
+## CVEs
+
+* CVE-2019-12900
+* CVE-2020-11023
+* CVE-2024-2236
+* CVE-2024-2511
+* CVE-2024-3596
+* CVE-2024-4603
+* CVE-2024-4741
+* CVE-2024-5535
+* CVE-2024-12797
+* CVE-2024-45338
+* CVE-2025-0395
+
+
+[NOTE]
+----
+For detailed information on Red Hat security ratings, review Severity ratings.
+----
+
 # Logging 5.9.13
 
 This release includes RHSA-2025:3906.

ocp-product-docs-plaintext/4.15/observability/monitoring/configuring-core-platform-monitoring/configuring-alerts-and-notifications.txt

@@ -400,6 +400,8 @@ Routing tree:
 ```
 
 
+* Send test alerts to Alertmanager in OpenShift 4 (Red Hat Customer Portal)
+
 ## Configuring alert routing with the Red Hat OpenShift Container Platform web console
 
 You can configure alert routing through the Red Hat OpenShift Container Platform web console to ensure that you learn about important issues with your cluster.
@@ -442,6 +444,8 @@ Alternatively, you can go to the same page through the notification drawer. Sele
 2. Click Add label to add further routing labels.
 6. Click Create to create the receiver.
 
+* Send test alerts to Alertmanager in OpenShift 4 (Red Hat Customer Portal)
+
 ## Configuring different alert receivers for default platform alerts and user-defined alerts
 
 You can configure different alert receivers for default platform alerts and user-defined alerts to ensure the following results:

ocp-product-docs-plaintext/4.15/observability/monitoring/configuring-core-platform-monitoring/configuring-metrics.txt

@@ -110,6 +110,9 @@ data:
 
 4. Save the file to apply the changes. The new configuration is applied automatically.
 
+* writeRelabelConfigs
+* relabel_config (Prometheus documentation)
+
 ## Supported remote write authentication settings
 
 You can use different methods to authenticate with a remote write endpoint. Currently supported authentication methods are AWS Signature Version 4, basic authentication, authorization, OAuth 2.0, and TLS client. The following table provides details about supported authentication methods for use with remote write.

ocp-product-docs-plaintext/4.15/observability/monitoring/configuring-user-workload-monitoring/configuring-alerts-and-notifications-uwm.txt

@@ -264,6 +264,8 @@ $ oc apply -f example-app-alert-routing.yaml
 
 The configuration is automatically applied to the Alertmanager pods.
 
+* Send test alerts to Alertmanager in OpenShift 4 (Red Hat Customer Portal)
+
 ## Configuring alert routing for user-defined projects with the Alertmanager secret
 
 If you have enabled a separate instance of Alertmanager that is dedicated to user-defined alert routing, you can customize where and how the instance sends notifications by editing the alertmanager-user-workload secret in the openshift-user-workload-monitoring namespace.
@@ -311,6 +313,8 @@ $ oc -n openshift-user-workload-monitoring create secret generic alertmanager-us
 ```
 
 
+* Send test alerts to Alertmanager in OpenShift 4 (Red Hat Customer Portal)
+
 ## Configuring different alert receivers for default platform alerts and user-defined alerts
 
 You can configure different alert receivers for default platform alerts and user-defined alerts to ensure the following results:

ocp-product-docs-plaintext/4.15/observability/monitoring/configuring-user-workload-monitoring/configuring-metrics-uwm.txt

@@ -110,6 +110,9 @@ data:
 
 4. Save the file to apply the changes. The new configuration is applied automatically.
 
+* writeRelabelConfigs
+* relabel_config (Prometheus documentation)
+
 ## Supported remote write authentication settings
 
 You can use different methods to authenticate with a remote write endpoint. Currently supported authentication methods are AWS Signature Version 4, basic authentication, authorization, OAuth 2.0, and TLS client. The following table provides details about supported authentication methods for use with remote write.

ocp-product-docs-plaintext/4.15/observability/monitoring/managing-alerts/managing-alerts-as-a-developer.txt

@@ -233,10 +233,10 @@ You can remove alerting rules for user-defined projects.
 * You are logged in as a cluster administrator or as a user that has the monitoring-rules-edit cluster role for the project where you want to create an alerting rule.
 * You have installed the OpenShift CLI (oc).
 
-* To remove rule <foo> in <namespace>, run the following:
+* To remove rule <alerting_rule> in <namespace>, run the following:
 
 ```terminal
-$ oc -n <namespace> delete prometheusrule <foo>
+$ oc -n <namespace> delete prometheusrule <alerting_rule>
 ```
 
 

ocp-product-docs-plaintext/4.15/observability/monitoring/managing-alerts/managing-alerts-as-an-administrator.txt

@@ -31,6 +31,7 @@ To obtain information about alerts:
 5. Click the name of an alert to view its Alert details page. The page includes a graph that illustrates alert time series data. It also provides the following information about the alert:
 * A description of the alert
 * Messages associated with the alert
+* A link to the runbook page on GitHub for the alert, if the page exists
 * Labels attached to the alert
 * A link to its governing alerting rule
 * Silences for the alert, if any exist
@@ -348,10 +349,10 @@ You can remove alerting rules for user-defined projects.
 * You are logged in as a cluster administrator or as a user that has the monitoring-rules-edit cluster role for the project where you want to create an alerting rule.
 * You have installed the OpenShift CLI (oc).
 
-* To remove rule <foo> in <namespace>, run the following:
+* To remove rule <alerting_rule> in <namespace>, run the following:
 
 ```terminal
-$ oc -n <namespace> delete prometheusrule <foo>
+$ oc -n <namespace> delete prometheusrule <alerting_rule>
 ```