Merge pull request #36974 from kalexand-rh/osdocs2368

osdocs-2368: updating 4.8 references to 4.9

Author: jeana-redhat

_topic_map.yml

@@ -81,8 +81,8 @@ Name: Release notes
 Dir: release_notes
 Distros: openshift-enterprise
 Topics:
-- Name: OpenShift Container Platform 4.8 release notes
-  File: ocp-4-8-release-notes
+- Name: OpenShift Container Platform 4.9 release notes
+  File: ocp-4-9-release-notes
 - Name: Versioning policy
   File: versioning-policy
 ---

logging/cluster-logging-release-notes.adoc

@@ -8,7 +8,14 @@ toc::[]
 [id="openshift-logging-supported-versions"]
 == Supported versions
 
-OpenShift Logging 5.0, 5.1, and 5.2 run on {product-title} 4.7 and 4.8.
+.{product-title} version support for Red Hat OpenShift Logging (RHOL)
+[options="header"]
+|====
+|        |4.7          |4.8          |4.9
+|RHOL 5.0|X            |X            |
+|RHOL 5.1|X            |X            |
+|RHOL 5.2|X            |X            |X
+|====
 
 include::modules/con_making-open-source-more-inclusive.adoc[leveloffset=+1]
 

logging/cluster-logging-upgrading.adoc

@@ -5,7 +5,14 @@ include::modules/common-attributes.adoc[]
 
 toc::[]
 
-{product-title} 4.7 and 4.8 support OpenShift Logging 5.0, 5.1, and 5.2.
+.{product-title} version support for Red Hat OpenShift Logging (RHOL)
+[options="header"]
+|====
+|        |4.7          |4.8          |4.9
+|RHOL 5.0|X            |X            |
+|RHOL 5.1|X            |X            |
+|RHOL 5.2|X            |X            |X
+|====
 
 To upgrade from cluster logging in {product-title} version 4.6 and earlier to OpenShift Logging 5.x, you update the {product-title} cluster to version 4.7 or 4.8. Then, you update the following operators:
 

metering/metering-upgrading-metering.adoc

@@ -46,11 +46,11 @@ Wait several seconds to allow the subscription to update before proceeding to th
 ====
 .  Click *Operators* -> *Installed Operators*.
 +
-The Metering Operator is shown as 4.8. For example:
+The Metering Operator is shown as 4.9. For example:
 +
 ----
 Metering
-4.8.0-202107012112.p0 provided by Red Hat, Inc
+4.9.0-202107012112.p0 provided by Red Hat, Inc
 ----
 
 .Verification
@@ -73,11 +73,11 @@ You can verify the metering upgrade by performing any of the following checks:
 $ oc get csv | grep metering
 ----
 +
-.Example output for metering upgrade from 4.7 to 4.8
+.Example output for metering upgrade from 4.8 to 4.9
 [source,terminal]
 ----
 NAME                                        DISPLAY                  VERSION                 REPLACES                                 PHASE
-metering-operator.4.8.0-202107012112.p0     Metering                 4.8.0-202107012112.p0   metering-operator.4.7.0-202007012112.p0  Succeeded
+metering-operator.4.9.0-202107012112.p0     Metering                 4.9.0-202107012112.p0   metering-operator.4.8.0-202007012112.p0  Succeeded
 ----
 --
 

migrating_from_ocp_3_to_4/planning-migration-3-4.adoc

@@ -8,7 +8,7 @@ toc::[]
 {product-title} {product-version} introduces architectural changes and enhancements. The procedures that you used to manage your {product-title} 3 cluster might not apply to {product-title} 4.
 
 ifndef::openshift-origin[]
-For information on configuring your {product-title} 4 cluster, review the appropriate sections of the {product-title} documentation. For information on new features and other notable technical changes, review the xref:../release_notes/ocp-4-8-release-notes.adoc#ocp-4-8-release-notes[OpenShift Container Platform 4.8 release notes].
+For information on configuring your {product-title} 4 cluster, review the appropriate sections of the {product-title} documentation. For information on new features and other notable technical changes, review the xref:../release_notes/ocp-4-9-release-notes.adoc#ocp-4-9-release-notes[OpenShift Container Platform 4.9 release notes].
 endif::[]
 
 It is not possible to upgrade your existing {product-title} 3 cluster to {product-title} 4. You must start with a new {product-title} 4 installation. Tools are available to assist in migrating your control plane settings and application workloads.

modules/cluster-logging-systemd-scaling.adoc

@@ -27,7 +27,7 @@ See "Creating machine configs with Butane" for information about Butane.
 [source,yaml]
 ----
 variant: openshift
-version: 4.8.0
+version: 4.9.0
 metadata:
   name: 40-worker-custom-journald
   labels:

modules/cluster-logging-updating-logging-to-5-0.adoc

@@ -7,7 +7,7 @@
 * The _Cluster Logging_ Operator became the _Red Hat OpenShift Logging_ Operator.
 * The _Elasticsearch_ Operator became _OpenShift Elasticsearch_ Operator.
 
-To upgrade from cluster logging in {product-title} version 4.6 and earlier to OpenShift Logging 5.x, you update the {product-title} cluster to version 4.7 or 4.8. Then, you update the following operators:
+To upgrade from cluster logging in {product-title} version 4.6 and earlier to OpenShift Logging 5.x, you update the {product-title} cluster to version 4.7, 4.8, or 4.9. Then, you update the following operators:
 
 * From Elasticsearch Operator 4.x to OpenShift Elasticsearch Operator 5.x
 * From Cluster Logging Operator 4.x to Red Hat OpenShift Logging Operator 5.x

modules/cluster-node-tuning-operator-verify-profiles.adoc

@@ -5,7 +5,7 @@
 [id="verifying-tuned-profiles-are-applied_{context}"]
 =  Verifying that the TuneD profiles are applied
 
-Starting with {product-title} 4.8, it is no longer necessary to check the TuneD pod logs
+It is no longer necessary to check the TuneD pod logs
 to find which TuneD profiles are applied on cluster nodes.
 
 [source,terminal]

modules/cnf-configure_for_irq_dynamic_load_balancing.adoc

@@ -44,7 +44,7 @@ metadata:
 spec:
   containers:
   - name: dynamic-irq-pod
-    image: "quay.io/openshift-kni/cnf-tests:4.8"
+    image: "quay.io/openshift-kni/cnf-tests:4.9"
     command: ["sleep", "10h"]
     resources:
       requests:

modules/cnf-installing-the-performance-addon-operator.adoc

@@ -75,7 +75,7 @@ $ oc get packagemanifest performance-addon-operator -n openshift-marketplace -o
 .Example output
 [source,terminal]
 ----
-4.8
+4.9
 ----
 
 .. Create the following Subscription CR and save the YAML in the `pao-sub.yaml` file: