Merge pull request #83448 from aireilly/TELCODOCS-1985-Day-2-Upgrades

TELCODOCS-1985: Day-2 upgrades for telco core clusters

Author: aireilly

.vale/styles/config/vocabularies/OpenShiftDocs/accept.txt

@@ -3,13 +3,14 @@
 [Ff]ronthaul
 [Mm][Bb]ps
 [Mm]idhaul
+[Oo]n-premise
 [Pp]assthrough
 [Pp]ostinstall
 [Pp]recaching
 [Pp]reinstall
-[Oo]n-premise
 [Rr]ealtime
 [Tt]elco
+[Uu]npause
 Assisted Installer
 Control Plane Machine Set Operator
 custom resources?

_topic_maps/_topic_map.yml

@@ -117,16 +117,16 @@ Topics:
   Dir: mirroring
   Distros: openshift-origin,openshift-enterprise
   Topics:
-    - Name: About disconnected installation mirroring
-      File: index
-    - Name: Creating a mirror registry with mirror registry for Red Hat OpenShift
-      File: installing-mirroring-creating-registry
-    - Name: Mirroring images for a disconnected installation by using the oc adm command
-      File: installing-mirroring-installation-images
-    - Name: Mirroring images for a disconnected installation using the oc-mirror plugin v1
-      File: installing-mirroring-disconnected
-    - Name: Mirroring images for a disconnected installation using oc-mirror plugin v2
-      File: about-installing-oc-mirror-v2
+  - Name: About disconnected installation mirroring
+    File: index
+  - Name: Creating a mirror registry with mirror registry for Red Hat OpenShift
+    File: installing-mirroring-creating-registry
+  - Name: Mirroring images for a disconnected installation by using the oc adm command
+    File: installing-mirroring-installation-images
+  - Name: Mirroring images for a disconnected installation using the oc-mirror plugin v1
+    File: installing-mirroring-disconnected
+  - Name: Mirroring images for a disconnected installation using oc-mirror plugin v2
+    File: about-installing-oc-mirror-v2
 - Name: Installing a cluster in a disconnected environment
   File: installing
 - Name: Using OLM in disconnected environments
@@ -135,22 +135,22 @@ Topics:
 - Name: Updating a cluster in a disconnected environment
   Dir: updating
   Topics:
-    - Name: About cluster updates in a disconnected environment
-      File: index
-    - Name: Mirroring OpenShift Container Platform images
-      File: mirroring-image-repository
-    - Name: Updating a cluster in a disconnected environment using OSUS
-      File: disconnected-update-osus
-      Distros: openshift-enterprise
-    - Name: Updating a cluster in a disconnected environment without OSUS
-      File: disconnected-update
-      Distros: openshift-enterprise
-    - Name: Updating a cluster in a disconnected environment by using the CLI
-      File: disconnected-update
-      Distros: openshift-origin
-    - Name: Uninstalling OSUS from a cluster
-      File: uninstalling-osus
-      Distros: openshift-enterprise
+  - Name: About cluster updates in a disconnected environment
+    File: index
+  - Name: Mirroring OpenShift Container Platform images
+    File: mirroring-image-repository
+  - Name: Updating a cluster in a disconnected environment using OSUS
+    File: disconnected-update-osus
+    Distros: openshift-enterprise
+  - Name: Updating a cluster in a disconnected environment without OSUS
+    File: disconnected-update
+    Distros: openshift-enterprise
+  - Name: Updating a cluster in a disconnected environment by using the CLI
+    File: disconnected-update
+    Distros: openshift-origin
+  - Name: Uninstalling OSUS from a cluster
+    File: uninstalling-osus
+    Distros: openshift-enterprise
 ---
 Name: Installing
 Dir: installing
@@ -2877,20 +2877,20 @@ Topics:
   - Name: Logging 6.0
     Dir: logging-6.0
     Topics:
-      - Name: Release notes
-        File: log6x-release-notes
-      - Name: About logging 6.0
-        File: log6x-about
-      - Name: Upgrading to Logging 6.0
-        File: log6x-upgrading-to-6
-      - Name: Configuring log forwarding
-        File: log6x-clf
-      - Name: Configuring LokiStack storage
-        File: log6x-loki
-      - Name: Visualization for logging
-        File: log6x-visual
-#      - Name: API reference 6.0
-#        File: log6x-api-reference
+    - Name: Release notes
+      File: log6x-release-notes
+    - Name: About logging 6.0
+      File: log6x-about
+    - Name: Upgrading to Logging 6.0
+      File: log6x-upgrading-to-6
+    - Name: Configuring log forwarding
+      File: log6x-clf
+    - Name: Configuring LokiStack storage
+      File: log6x-loki
+    - Name: Visualization for logging
+      File: log6x-visual
+    # - Name: API reference 6.0
+    #   File: log6x-api-reference
   - Name: Support
     File: cluster-logging-support
   - Name: Troubleshooting logging
@@ -3347,6 +3347,29 @@ Topics:
     File: ibi-factory-image-based-install
   - Name: Deploying single-node OpenShift using the installation program
     File: ibi-edge-image-based-install-standalone
+- Name: Day 2 operations for telco core CNF clusters
+  Dir: day_2_core_cnf_clusters
+  Distros: openshift-origin,openshift-enterprise
+  Topics:
+  - Name: Upgrading telco core CNF clusters
+    Dir: updating
+    Topics:
+    - Name: Upgrading telco core CNF clusters
+      File: telco-update-welcome
+    - Name: OpenShift Container Platform API compatibility
+      File: telco-update-api
+    - Name: Preparing for the cluster update
+      File: telco-update-ocp-update-prep
+    - Name: Managing live CNF pods during the cluster update
+      File: telco-update-cnf-update-prep
+    - Name: Before you update the cluster
+      File: telco-update-before-the-update
+    - Name: Completing the Control Plane Only update
+      File: telco-update-completing-the-control-plane-only-update
+    - Name: Completing the y-stream update
+      File: telco-update-completing-the-y-stream-update
+    - Name: Completing the z-stream update
+      File: telco-update-completing-the-z-stream-update
 ---
 Name: Specialized hardware and driver enablement
 Dir: hardware_enablement

backup_and_restore/control_plane_backup_and_restore/backing-up-etcd.adoc

@@ -10,7 +10,7 @@ etcd is the key-value store for {product-title}, which persists the state of all
 
 Back up your cluster's etcd data regularly and store in a secure location ideally outside the {product-title} environment. Do not take an etcd backup before the first certificate rotation completes, which occurs 24 hours after installation, otherwise the backup will contain expired certificates. It is also recommended to take etcd backups during non-peak usage hours because the etcd snapshot has a high I/O cost.
 
-Be sure to take an etcd backup after you upgrade your cluster. This is important because when you restore your cluster, you must use an etcd backup that was taken from the same z-stream release. For example, an {product-title} 4.y.z cluster must use an etcd backup that was taken from 4.y.z.
+Be sure to take an etcd backup after you update your cluster. This is important because when you restore your cluster, you must use an etcd backup that was taken from the same z-stream release. For example, an {product-title} 4.y.z cluster must use an etcd backup that was taken from 4.y.z.
 
 [IMPORTANT]
 ====
@@ -29,5 +29,5 @@ include::modules/backup-etcd.adoc[leveloffset=+1]
 
 // Creating automated etcd backups
 include::modules/etcd-creating-automated-backups.adoc[leveloffset=+1]
-include::modules/creating-single-etcd-backup.adoc[leveloffset=+1]
-include::modules/creating-recurring-etcd-backups.adoc[leveloffset=+1]
+include::modules/creating-single-etcd-backup.adoc[leveloffset=+2]
+include::modules/creating-recurring-etcd-backups.adoc[leveloffset=+2]

edge_computing/day_2_core_cnf_clusters/_attributes

@@ -0,0 +1 @@
+../../_attributes/

edge_computing/day_2_core_cnf_clusters/images

@@ -0,0 +1 @@
+../../images/

edge_computing/day_2_core_cnf_clusters/modules

@@ -0,0 +1 @@
+../../modules/

edge_computing/day_2_core_cnf_clusters/snippets

@@ -0,0 +1 @@
+../../snippets/

edge_computing/day_2_core_cnf_clusters/updating/_attributes

@@ -0,0 +1 @@
+../../../_attributes/

edge_computing/day_2_core_cnf_clusters/updating/images

@@ -0,0 +1 @@
+../../../images/

edge_computing/day_2_core_cnf_clusters/updating/modules

@@ -0,0 +1 @@
+../../../modules/