Merge pull request #109069 from lahinson/osdocs-16094-hcp-hc-shared-namespace

[OSDOCS-16095]: Adding note about shared namespaces to HCP on Virt DR docs

Author: mburke5678

modules/backup-hosted-cluster-virt.adoc

@@ -6,6 +6,7 @@
 [id="backup-hosted-cluster-virt_{context}"]
 = Backing up a hosted cluster on {VirtProductName}
 
+[role="_abstract"]
 When you back up a hosted cluster on {VirtProductName}, the hosted cluster can remain running. The backup contains the hosted control plane components and the etcd for the hosted cluster.
 
 When the hosted cluster is not running compute nodes on external infrastructure, hosted cluster workload data that is stored in persistent volume claims (PVCs) that are provisioned by KubeVirt CSI are also backed up. The backup does not contain any KubeVirt virtual machines (VMs) that are used as compute nodes. Those VMs are automatically re-created after the restore process is completed.
@@ -24,7 +25,7 @@ metadata:
   labels:
     velero.io/storage-location: default
 spec:
-  includedNamespaces: <1>
+  includedNamespaces:
   - clusters
   - clusters-hosted
   includedResources:
@@ -49,23 +50,31 @@ spec:
   - service
   - route
   excludedResources: [ ]
-  labelSelector: <2>
+  labelSelector:
     matchExpressions:
     - key: 'hypershift.openshift.io/is-kubevirt-rhcos'
       operator: 'DoesNotExist'
   storageLocation: default
   preserveNodePorts: true
   ttl: 4h0m0s
-  snapshotMoveData: true <3>
-  datamover: "velero" <4>
-  defaultVolumesToFsBackup: false <5>
+  snapshotMoveData: true
+  datamover: "velero"
+  defaultVolumesToFsBackup: false
 ----
 +
-<1> This field selects the namespaces from the objects to back up. Include namespaces from both the hosted cluster and the hosted control plane. In this example, `clusters` is a namespace from the hosted cluster and `clusters-hosted` is a namespace from the hosted control plane. By default, the `HostedControlPlane` namespace is `clusters-<hosted_cluster_name>`.
-<2> The boot image of the VMs that are used as the hosted cluster nodes are stored in large PVCs. To reduce backup time and storage size, you can filter those PVCs out of the backup by adding this label selector.
-<3> This field and the `datamover` field enable automatically uploading the CSI `VolumeSnapshots` to remote cloud storage.
-<4> This field and the `snapshotMoveData` field enable automatically uploading the CSI `VolumeSnapshots` to remote cloud storage.
-<5> This field indicates whether pod volume file system backup is used for all volumes by default. Set this value to `false` to back up the PVCs that you want.
+where:
++
+`includedNamespaces`:: Specifies the namespaces from the objects to back up. Include namespaces from both the hosted cluster and the hosted control plane. In this example, `clusters` is a namespace from the hosted cluster and `clusters-hosted` is a namespace from the hosted control plane.
++
+[IMPORTANT]
+====
+If you store all hosted cluster information in a shared namespace and then back up and restore a hosted cluster, you might unintentionally change other hosted clusters. To avoid this issue, do not store all hosted cluster information in a shared namespace. Alternatively, you can back up and restore resources based on labels.
+====
++
+`labelSelector`:: Specifies the boot image of the VMs that are used as the hosted cluster nodes are stored in large PVCs. To reduce backup time and storage size, you can filter those PVCs out of the backup by adding this label selector.
+`snapshotMoveData`:: Along with the `datamover` field, specifies that the CSI `VolumeSnapshots` are automatically uploaded to remote cloud storage.
+`datamover`:: Along with the `snapshotMoveData` field, specifies that the CSI `VolumeSnapshots` are automatically uploaded to remote cloud storage.
+`defaultVolumesToFsBackup`:: Specifies whether pod volume file system backup is used for all volumes by default. Set this value to `false` to back up the PVCs that you want.
 
 . Apply the changes to the YAML file by entering the following command:
 +