Merge branch 'openshift:main' into cp_latency

Author: shahsahil264

_topic_maps/_topic_map.yml

@@ -1303,6 +1303,16 @@ Topics:
     File: ovn-k-banp
   - Name: Understanding the Ingress Node Firewall Operator
     File: ingress-node-firewall-operator
+  - Name: Egress Firewall
+    Dir: egress_firewall
+    Distros: openshift-enterprise,openshift-origin
+    Topics:
+    - Name: Viewing an egress firewall for a project
+      File: viewing-egress-firewall-ovn
+    - Name: Editing an egress firewall for a project
+      File: editing-egress-firewall-ovn
+    - Name: Removing an egress firewall from a project
+      File: removing-egress-firewall-ovn
   - Name: Configuring an egress firewall for a project
     File: configuring-egress-firewall-ovn
   - Name: Configuring IPsec encryption
@@ -1470,12 +1480,6 @@ Topics:
     File: logging-network-policy
   - Name: Configure an external gateway on the default network
     File: configuring-secondary-external-gateway
-  - Name: Viewing an egress firewall for a project
-    File: viewing-egress-firewall-ovn
-  - Name: Editing an egress firewall for a project
-    File: editing-egress-firewall-ovn
-  - Name: Removing an egress firewall from a project
-    File: removing-egress-firewall-ovn
   - Name: Configuring an egress IP address
     File: configuring-egress-ips-ovn
   - Name: Assigning an egress IP address
@@ -1662,8 +1666,6 @@ Topics:
       File: persistent-storage-hostpath
     - Name: Persistent storage using LVM Storage
       File: persistent-storage-using-lvms
-    - Name: Troubleshooting local persistent storage using LVMS
-      File: troubleshooting-local-persistent-storage-using-lvms
 - Name: Using Container Storage Interface (CSI)
   Dir: container_storage_interface
   Distros: openshift-enterprise,openshift-origin
@@ -1862,9 +1864,6 @@ Topics:
   - Name: Catalog source pod scheduling
     File: olm-cs-podsched
     Distros: openshift-origin,openshift-enterprise
-  - Name: Managing platform Operators
-    File: olm-managing-po
-    Distros: openshift-enterprise,openshift-origin
   - Name: Troubleshooting Operator issues
     File: olm-troubleshooting-operator-issues
     Distros: openshift-enterprise,openshift-origin
@@ -2156,27 +2155,6 @@ Topics:
   File: odc-viewing-application-composition-using-topology-view
 - Name: Exporting applications
   File: odc-exporting-applications
-- Name: Connecting applications to services
-  Dir: connecting_applications_to_services
-  Topics:
-  - Name: Service Binding Operator release notes
-    File: sbo-release-notes
-  - Name: Understanding Service Binding Operator
-    File: understanding-service-binding-operator
-  - Name: Installing Service Binding Operator
-    File: installing-sbo
-  - Name: Getting started with service binding
-    File: getting-started-with-service-binding
-  - Name: Getting started with service binding on IBM Power, IBM Z, and IBM LinuxONE
-    File: getting-started-with-service-binding-ibm-power-ibm-z
-  - Name: Exposing binding data from a service
-    File: exposing-binding-data-from-a-service
-  - Name: Projecting binding data
-    File: projecting-binding-data
-  - Name: Binding workloads using Service Binding Operator
-    File: binding-workloads-using-sbo
-  - Name: Connecting an application to a service using the Developer perspective
-    File: odc-connecting-an-application-to-a-service-using-the-developer-perspective
 - Name: Working with Helm charts
   Dir: working_with_helm_charts
   Topics:
@@ -2324,7 +2302,7 @@ Topics:
       File: cpmso-config-options-gcp
     - Name: Control plane configuration options for Nutanix
       File: cpmso-config-options-nutanix
-    - Name: Control plane configuration options for Red Hat OpenStack
+    - Name: Control plane configuration options for Red Hat OpenStack Platform
       File: cpmso-config-options-openstack
     - Name: Control plane configuration options for VMware vSphere
       File: cpmso-config-options-vsphere
@@ -2371,6 +2349,8 @@ Topics:
   File: hcp-getting-started
 - Name: Authentication and authorization for hosted control planes
   File: hcp-authentication-authorization
+- Name: Handling a machine configuration for hosted control planes
+  File: hcp-machine-config
 - Name: Using feature gates in a hosted cluster
   File: hcp-using-feature-gates
 - Name: Updating hosted control planes
@@ -2625,6 +2605,8 @@ Topics:
     File: nodes-sno-worker-nodes
 - Name: Node metrics dashboard
   File: nodes-dashboard-using
+- Name: Manage secure signatures with sigstore
+  File: nodes-sigstore-using
 ---
 Name: Windows Container Support for OpenShift
 Dir: windows_containers
@@ -2823,8 +2805,8 @@ Topics:
   - Name: Release notes
     Dir: distr_tracing_rn
     Topics:
-    - Name: Distributed tracing 3.1.1
-      File: distr-tracing-rn-3-1-1
+    - Name: Distributed tracing 3.2
+      File: distr-tracing-rn-3-2
     - Name: Past releases
       File: distr-tracing-rn-past-releases
   - Name: Distributed tracing architecture
@@ -2861,8 +2843,8 @@ Topics:
   - Name: Release notes
     Dir: otel_rn
     Topics:
-    - Name: Red Hat build of OpenTelemetry 3.1.1
-      File: otel-rn-3-1-1
+    - Name: Red Hat build of OpenTelemetry 3.2
+      File: otel-rn-3-2
     - Name: Past releases
       File: otel-rn-past-releases
   - Name: Installing
@@ -2873,8 +2855,8 @@ Topics:
     File: otel-configuration-of-instrumentation
   - Name: Sending traces and metrics to the Collector
     File: otel-sending-traces-and-metrics-to-otel-collector
-  - Name: Sending metrics to the monitoring stack
-    File: otel-config-send-metrics-monitoring-stack
+  - Name: Configuring metrics for the monitoring stack
+    File: otel-configuring-metrics-for-monitoring-stack
   - Name: Forwarding traces to a TempoStack
     File: otel-forwarding
   - Name: Configuring the Collector metrics
@@ -3051,8 +3033,30 @@ Topics:
   File: ztp-sno-additional-worker-node
 - Name: Pre-caching images for single-node OpenShift deployments
   File: ztp-precaching-tool
-- Name: Image-based upgrade for single-node OpenShift clusters
-  File: ztp-image-based-upgrade
+#- Name: Image-based upgrade for single-node OpenShift clusters
+#  Dir: image_based_upgrade
+#  Distros: openshift-origin,openshift-enterprise
+#  Topics:
+#  - Name: Understanding the image-based upgrade for single-node OpenShift clusters
+#    File: cnf-understanding-image-based-upgrade
+#  - Name: Preparing for an image-based upgrade for single-node OpenShift clusters
+#    Dir: preparing_for_image_based_upgrade
+#    Distros: openshift-origin,openshift-enterprise
+#    Topics:
+#    - Name: Configuring a shared container directory for the image-based upgrade
+#      File: cnf-image-based-upgrade-shared-container-image
+#    - Name: Installing Operators for the image-based upgrade
+#      File: cnf-image-based-upgrade-install-operators
+#    - Name: Generating a seed image for the image-based upgrade with Lifecycle Agent
+#      File: cnf-image-based-upgrade-generate-seed
+#    - Name: Creating ConfigMap objects for the image-based upgrade with Lifecycle Agent
+#      File: cnf-image-based-upgrade-prep-resources
+#    - Name: Creating ConfigMap objects for the image-based upgrade with Lifecycle Agent using GitOps ZTP
+#      File: ztp-image-based-upgrade-prep-resources
+#  - Name: Performing an image-based upgrade for single-node OpenShift clusters
+#    File: cnf-image-based-upgrade-base
+#  - Name: Performing an image-based upgrade for single-node OpenShift clusters using GitOps ZTP
+#    File: ztp-image-based-upgrade
 ---
 Name: Reference design specifications
 Dir: telco_ref_design_specs

_topic_maps/_topic_map_osd.yml

@@ -716,8 +716,6 @@ Topics:
     File: olm-managing-custom-catalogs
   - Name: Catalog source pod scheduling
     File: olm-cs-podsched
-# - Name: Managing platform Operators  <= Tech Preview
-#   File: olm-managing-po
   - Name: Troubleshooting Operator issues
     File: olm-troubleshooting-operator-issues
 - Name: Developing Operators
@@ -893,28 +891,6 @@ Topics:
 # cannot create required namespace
 # - Name: Exporting applications
 #  File: odc-exporting-applications
-- Name: Connecting applications to services
-  Dir: connecting_applications_to_services
-  Topics:
-  - Name: Service Binding Operator release notes
-    File: sbo-release-notes
-  - Name: Understanding Service Binding Operator
-    File: understanding-service-binding-operator
-  - Name: Installing Service Binding Operator
-    File: installing-sbo
-  - Name: Getting started with service binding
-    File: getting-started-with-service-binding
-# Not applicable to ROSA/OSD
-#  - Name: Getting started with service binding on IBM Power, IBM Z, and IBM LinuxONE
-#    File: getting-started-with-service-binding-ibm-power-ibm-z
-  - Name: Exposing binding data from a service
-    File: exposing-binding-data-from-a-service
-  - Name: Projecting binding data
-    File: projecting-binding-data
-  - Name: Binding workloads using Service Binding Operator
-    File: binding-workloads-using-sbo
-  - Name: Connecting an application to a service using the Developer perspective
-    File: odc-connecting-an-application-to-a-service-using-the-developer-perspective
 - Name: Working with Helm charts
   Dir: working_with_helm_charts
   Topics:

_topic_maps/_topic_map_rosa.yml

@@ -937,8 +937,6 @@ Topics:
     File: olm-managing-custom-catalogs
   - Name: Catalog source pod scheduling
     File: olm-cs-podsched
-# - Name: Managing platform Operators  <= Tech Preview
-#   File: olm-managing-po
   - Name: Troubleshooting Operator issues
     File: olm-troubleshooting-operator-issues
 - Name: Developing Operators
@@ -1128,28 +1126,6 @@ Topics:
 # cannot create required namespace
 # - Name: Exporting applications
 #  File: odc-exporting-applications
-- Name: Connecting applications to services
-  Dir: connecting_applications_to_services
-  Topics:
-  - Name: Service Binding Operator release notes
-    File: sbo-release-notes
-  - Name: Understanding Service Binding Operator
-    File: understanding-service-binding-operator
-  - Name: Installing Service Binding Operator
-    File: installing-sbo
-  - Name: Getting started with service binding
-    File: getting-started-with-service-binding
-# Not applicable to ROSA/OSD
-#  - Name: Getting started with service binding on IBM Power, IBM Z, and IBM LinuxONE
-#    File: getting-started-with-service-binding-ibm-power-ibm-z
-  - Name: Exposing binding data from a service
-    File: exposing-binding-data-from-a-service
-  - Name: Projecting binding data
-    File: projecting-binding-data
-  - Name: Binding workloads using Service Binding Operator
-    File: binding-workloads-using-sbo
-  - Name: Connecting an application to a service using the Developer perspective
-    File: odc-connecting-an-application-to-a-service-using-the-developer-perspective
 - Name: Working with Helm charts
   Dir: working_with_helm_charts
   Topics:
@@ -1367,8 +1343,8 @@ Topics:
 #    File: nodes-nodes-managing-max-pods
   - Name: Using the Node Tuning Operator
     File: nodes-node-tuning-operator
-  - Name: Remediating, fencing, and maintaining nodes
-    File: nodes-remediating-fencing-maintaining-rhwa
+#  - Name: Remediating, fencing, and maintaining nodes
+#    File: nodes-remediating-fencing-maintaining-rhwa
 # Cannot create namespace needed to oc debug and reboot; revisit after Operator book converted
 #  - Name: Understanding node rebooting
 #    File: nodes-nodes-rebooting
@@ -1387,8 +1363,8 @@ Topics:
 #    Distros: openshift-rosa
 #  - Name: Monitoring for problems in your nodes
 #    File: nodes-nodes-problem-detector
-  - Name: Machine Config Daemon metrics
-    File: nodes-nodes-machine-config-daemon-metrics
+#  - Name: Machine Config Daemon metrics
+#    File: nodes-nodes-machine-config-daemon-metrics
 # cannot patch resource "nodes"
 #  - Name: Creating infrastructure nodes
 #    File: nodes-nodes-creating-infrastructure-nodes

_topic_maps/_topic_map_rosa_hcp.yml

@@ -940,8 +940,6 @@ Topics:
 #     File: olm-managing-custom-catalogs
 #   - Name: Catalog source pod scheduling
 #     File: olm-cs-podsched
-#  - Name: Managing platform Operators  <= Tech Preview
-#    File: olm-managing-po
 #   - Name: Troubleshooting Operator issues
 #     File: olm-troubleshooting-operator-issues
 # - Name: Developing Operators
@@ -1117,28 +1115,6 @@ Topics:
 #  cannot create required namespace
 #  - Name: Exporting applications
 #   File: odc-exporting-applications
-# - Name: Connecting applications to services
-#   Dir: connecting_applications_to_services
-#   Topics:
-#   - Name: Service Binding Operator release notes
-#     File: sbo-release-notes
-#   - Name: Understanding Service Binding Operator
-#     File: understanding-service-binding-operator
-#   - Name: Installing Service Binding Operator
-#     File: installing-sbo
-#   - Name: Getting started with service binding
-#     File: getting-started-with-service-binding
-#  Not applicable to ROSA/OSD
-#   - Name: Getting started with service binding on IBM Power, IBM Z, and IBM LinuxONE
-#     File: getting-started-with-service-binding-ibm-power-ibm-z
-#   - Name: Exposing binding data from a service
-#     File: exposing-binding-data-from-a-service
-#   - Name: Projecting binding data
-#     File: projecting-binding-data
-#   - Name: Binding workloads using Service Binding Operator
-#     File: binding-workloads-using-sbo
-#   - Name: Connecting an application to a service using the Developer perspective
-#     File: odc-connecting-an-application-to-a-service-using-the-developer-perspective
 # - Name: Working with Helm charts
 #   Dir: working_with_helm_charts
 #   Topics:

applications/index.adoc

@@ -39,14 +39,6 @@ After you create the application, you can use the web console to xref:../applica
 
 When the application is running, not all applications resources are used. As a cluster administrator, you can choose to xref:../applications/idling-applications.adoc#idling-applications[idle these scalable resources] to reduce resource consumption.
 
-[id="connecting-application"]
-=== Connecting an application to services
-
-An application uses backing services to build and connect workloads, which vary according to the service provider. Using the xref:../applications/connecting_applications_to_services/understanding-service-binding-operator.adoc#understanding-service-binding-operator[Service Binding Operator], as a developer, you can bind workloads together with Operator-managed backing services, without any manual procedures to configure the binding connection.
-ifndef::openshift-dedicated,openshift-rosa[]
-You can apply service binding also on xref:../applications/connecting_applications_to_services/getting-started-with-service-binding-ibm-power-ibm-z.adoc#getting-started-with-service-binding-ibm-power-ibm-z[IBM Power Systems, IBM Z, and LinuxONE environments].
-endif::openshift-dedicated,openshift-rosa[]
-
 [id="deploying-application"]
 === Deploying an application
 You can deploy your application using xref:../applications/deployments/what-deployments-are.adoc#what-deployments-are[`Deployment` or `DeploymentConfig`] objects and xref:../applications/deployments/managing-deployment-processes.adoc#deployment-operations[manage] them from the web console. You can create xref:../applications/deployments/deployment-strategies.adoc#deployment-strategies[deployment strategies] that help reduce downtime during a change or an upgrade to the application.

applications/odc-viewing-application-composition-using-topology-view.adoc

@@ -14,7 +14,6 @@ To view your applications in the *Topology* view and interact with them, ensure
 ifndef::openshift-rosa,openshift-dedicated[]
 * You have xref:../web_console/web-console.adoc#web-console[logged in to the web console].
 * You have the appropriate xref:../authentication/using-rbac.adoc#default-roles_using-rbac[roles and permissions] in a project to create applications and other workloads in {product-title}.
-* You have xref:../applications/creating_applications/odc-creating-applications-using-developer-perspective.adoc#odc-creating-applications-using-developer-perspective[created and deployed an application on {product-title} using the *Developer* perspective].
 * You are in xref:../web_console/web-console-overview.adoc#about-developer-perspective_web-console-overview[the *Developer* perspective].
 endif::openshift-rosa,openshift-dedicated[]
 ifdef::openshift-rosa,openshift-dedicated[]
@@ -42,7 +41,6 @@ include::modules/odc-labels-and-annotations-used-for-topology-view.adoc[leveloff
 == Additional resources
 
 * See xref:../applications/creating_applications/odc-creating-applications-using-developer-perspective.adoc#odc-importing-codebase-from-git-to-create-application_odc-creating-applications-using-developer-perspective[Importing a codebase from Git to create an application] for more information on creating an application from Git.
-* See xref:../applications/connecting_applications_to_services/odc-connecting-an-application-to-a-service-using-the-developer-perspective.adoc#odc-connecting-an-application-to-a-service-using-the-developer-perspective[Connecting an application to a service using the Developer perspective].
 ifndef::openshift-rosa,openshift-dedicated[]
 * See xref:../applications/odc-exporting-applications.adoc#odc-exporting-applications[Exporting applications].
 endif::openshift-rosa,openshift-dedicated[]

architecture/control-plane.adoc

@@ -50,17 +50,6 @@ include::modules/arch-olm-operators.adoc[leveloffset=+2]
 * For more details on running add-on Operators in {product-title}, see the _Operators_ guide sections on xref:../operators/understanding/olm/olm-understanding-olm.adoc#olm-understanding-olm[Operator Lifecycle Manager (OLM)] and xref:../operators/understanding/olm-understanding-operatorhub.adoc#olm-understanding-operatorhub[OperatorHub].
 * For more details on the Operator SDK, see xref:../operators/operator_sdk/osdk-about.adoc#osdk-about[Developing Operators].
 
-ifdef::openshift-enterprise,openshift-webscale,openshift-origin[]
-include::modules/arch-platform-operators.adoc[leveloffset=+2]
-
-[role="_additional-resources"]
-.Additional resources
-* xref:../operators/admin/olm-managing-po.adoc#olm-managing-po[Managing platform Operators]
-* xref:../operators/admin/olm-managing-po.adoc#olm-po-techpreview_olm-managing-po[Technology Preview restrictions for platform Operators]
-* xref:../operators/understanding/olm-packaging-format.adoc#olm-rukpak-about_olm-packaging-format[RukPak component and packaging format]
-* xref:../installing/cluster-capabilities.adoc#cluster-capabilities[Cluster capabilities]
-endif::[]
-
 // This module does not apply to OSD/ROSA
 ifndef::openshift-dedicated,openshift-rosa[]
 include::modules/understanding-machine-config-operator.adoc[leveloffset=+1]

authentication/using-service-accounts-in-applications.adoc

@@ -12,12 +12,6 @@ include::modules/service-accounts-default.adoc[leveloffset=+1]
 
 include::modules/service-account-auto-secret-removed.adoc[leveloffset=+2]
 
-.Additional resources
-
-* For information about requesting bound service account tokens, see xref:../authentication/bound-service-account-tokens.adoc#bound-sa-tokens-configuring_bound-service-account-tokens[Configuring bound service account tokens using volume projection].
-
-* For information about creating a service account token secret, see xref:../nodes/pods/nodes-pods-secrets.adoc#nodes-pods-secrets-creating-sa_nodes-pods-secrets[Creating a service account token secret].
-
 include::modules/service-accounts-creating.adoc[leveloffset=+1]
 
 // include::modules/service-accounts-using-credentials-inside-a-container.adoc[leveloffset=+1]

cloud_experts_tutorials/cloud-experts-rosa-cloudwatch-sts.adoc

@@ -226,7 +226,7 @@ EOF
 $ aws logs describe-log-groups --log-group-name-prefix rosa-${ROSA_CLUSTER_NAME}
 ----
 +
-.Sample output
+.Example output
 +
 [source,c]
 ----

cloud_experts_tutorials/rosa-mobb-prerequisites-tutorial.adoc

@@ -107,7 +107,7 @@ $ aws configure
 $ aws configure
 ----
 +
-.Sample output
+.Example output
 [source,terminal]
 ----
 AWS Access Key ID []:
@@ -127,7 +127,7 @@ $ aws sts get-caller-identity
 +
 You should receive output similar to the following:
 +
-.Sample output
+.Example output
 [source,terminal]
 ----
 {