OADP 2419 Release Notes F

Author: CarmiWisemon

backup_and_restore/application_backup_and_restore/oadp-release-notes.adoc

@@ -9,6 +9,8 @@ toc::[]
 
 The release notes for OpenShift API for Data Protection (OADP) describe new features and enhancements, deprecated features, product recommendations, known issues, and resolved issues.
 
+include::modules/oadp-release-notes-1-3-0.adoc[leveloffset=+1]
+
 include::modules/oadp-release-notes-1-2-3.adoc[leveloffset=+1]
 
 include::modules/oadp-release-notes-1-2-2.adoc[leveloffset=+1]

modules/oadp-release-notes-1-2-0.adoc

@@ -43,3 +43,140 @@ The HTTP/2 protocol is susceptible to a denial of service attack because request
 It is advised to upgrade to OADP 1.2.3, which resolves this issue.
 
 For more information, see link:https://access.redhat.com/security/cve/cve-2023-39325[CVE-2023-39325 (Rapid Reset Attack)].
+
+[id="Upgrade-notes-1-2-0_{context}"]
+== Upgrade notes
+
+[NOTE]
+====
+Always upgrade to next minor version, *do not* skip versions. To update to a later version, upgrade only one channel at a time. For example: to upgrade from OpenShift API for Data Protection (OADP) 1.1 to 1.3, upgrade first to 1.2, then to 1.3.
+====
+
+[id="changes-oadp-1-1-to-1-2_{context}"]
+=== Changes from OADP 1.1 to 1.2
+
+The Velero server was updated from version 1.9 to 1.11
+
+In OpenShift API for Data Protection (OADP) 1.2 the DataProtectionApplication (DPA) configuration `spec.configuration.velero.args` has changed:
+
+* The `default-volumes-to-restic` field was renamed `default-volumes-to-fs-backup`, if you use `spec.velero`, you need to add it again with the new name to your DPA, after upgrading the OADP.
+
+* The `default-restic-prune-frequency` field was renamed `default-repo-maintain-frequency`, if you use `spec.velero`, you need to add it again with the new name to your DPA, after upgrading the OADP.
+
+* The `restic-timeout` field was renamed `fs-backup-timeout`, if you are use `spec.velero`, you need to add it again with the new name to your DPA, after upgrading the OADP.
+
+* The `restic` DaemonSet was renamed `node-agent`. OADP will automatically update the name of the DaemonSet.
+
+* The CustomResourceDefinition `resticrepositories.velero.io` was renamed `backuprepositories.velero.io`.
+
+** The CustomResourceDefinition `resticrepositories.velero.io` can be removed from the cluster.
+
+[id="upgrade-steps-1-2-0_{context}"]
+=== Upgrade steps
+
+[id="backing-up-dpa-configuration-1-2-0_{context}"]
+==== Backing up the DPA configuration
+
+Save your current DataProtectionApplication (DPA) CustomResource configuration and verify that you saved the values.
+
+.Example
+[source,terminal]
+----
+oc get dpa -n openshift-adp -o yaml > dpa.orig.backup
+----
+
+[id="upgrading-dpa-operator-1-2-0_{context}"]
+==== Upgrading the OADP Operator
+
+* Change your subscription channel for the OADP Operator from `stable-1.1` to `stable-1.2`.
+* Allow time for the Operator and containers to update and restart.
+
+For general operator upgrade instructions review the https://docs.openshift.com/container-platform/4.14/operators/admin/olm-upgrading-operators.html[OpenShift documentation].
+
+[id="converting-dpa-1-2-0_{context}"]
+==== Converting DPA to the new version
+
+If you use fields that were updated in `spec.configuration.velero.args`, you need to update the new names.
+
+.Example
+[source,yaml]
+----
+  spec:
+   configuration:
+     velero:
+       args:
+-        default-volumes-to-restic: true
++        default-volumes-to-fs-backup: true
+-        default-restic-prune-frequency: 6000
++        default-repo-maintain-frequency: 6000
+-        restic-timeout: 600
++        fs-backup-timeout: 600
+# ...
+----
+Wait for the DPA to reconcile successfully.
+
+[id="verifying-upgrade-1-2-0_{context}"]
+==== Verifying the upgrade
+
+////
+After the 1.2 and earlier DPA is merged this sentence and xref will be used instead of the content below.
+* Follow the instructions to xref:../../../oadp-installing-dpa-1-2-and-earlier.adoc#verifying-oadp-installation-1-2_installing-oadp-aws[verify the installation].
+////
+
+. Verify the installation by viewing the OADP resources by running the following command:
++
+[source,terminal]
+----
+$ oc get all -n openshift-adp
+----
++
+.Example output
++
+----
+NAME                                                     READY   STATUS    RESTARTS   AGE
+pod/oadp-operator-controller-manager-67d9494d47-6l8z8    2/2     Running   0          2m8s
+pod/restic-9cq4q                                         1/1     Running   0          94s
+pod/restic-m4lts                                         1/1     Running   0          94s
+pod/restic-pv4kr                                         1/1     Running   0          95s
+pod/velero-588db7f655-n842v                              1/1     Running   0          95s
+
+NAME                                                       TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)    AGE
+service/oadp-operator-controller-manager-metrics-service   ClusterIP   172.30.70.140    <none>        8443/TCP   2m8s
+
+NAME                    DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR   AGE
+daemonset.apps/restic   3         3         3       3            3           <none>          96s
+
+NAME                                                READY   UP-TO-DATE   AVAILABLE   AGE
+deployment.apps/oadp-operator-controller-manager    1/1     1            1           2m9s
+deployment.apps/velero                              1/1     1            1           96s
+
+NAME                                                           DESIRED   CURRENT   READY   AGE
+replicaset.apps/oadp-operator-controller-manager-67d9494d47    1         1         1       2m9s
+replicaset.apps/velero-588db7f655                              1         1         1       96s
+----
+
+.  Verify that the DPA is reconciled by running the following command:
++
+[source,terminal]
+----
+oc get dpa dpa-sample -n openshift-adp -o jsonpath='{.status}'
+----
+.Example output
+[source,yaml]
++
+----
+{"conditions":[{"lastTransitionTime":"2023-10-27T01:23:57Z","message":"Reconcile complete","reason":"Complete","status":"True","type":"Reconciled"}]}
+----
+
+. Verify the `type` is set to `Reconciled`.
+
+. Verify the `BackupStorageLocation` by running the following command:
++
+[source,terminal]
+----
+oc get backupStorageLocation -n openshift-adp
+NAME           PHASE       LAST VALIDATED   AGE     DEFAULT
+dpa-sample-1   Available   1s               3d16h   true
+----
+
+. Verify that the `PHASE` is in `Available`.