Add discovered application samples

dr/discovered/deployment-rbd/drpc.yaml

@@ -0,0 +1,26 @@
+---
+apiVersion: ramendr.openshift.io/v1alpha1
+kind: DRPlacementControl
+metadata:
+  name: drpc
+spec:
+  preferredCluster: dr1
+  drPolicyRef:
+    name: dr-policy
+  placementRef:
+    kind: Placement
+    # Match kustomization namePrefix
+    name: deployment-rbd-placement
+    namespace: ramen-ops
+  pvcSelector:
+    matchLabels:
+      appname: busybox
+  protectedNamespaces:
+    - deployment-rbd
+  kubeObjectProtection:
+    kubeObjectSelector:
+      matchExpressions:
+        - key: appname
+          operator: In
+          values:
+            - busybox

dr/discovered/deployment-rbd/kustomization.yaml

@@ -0,0 +1,9 @@
+---
+namespace: ramen-ops
+namePrefix: deployment-rbd-
+commonLabels:
+  app: deployment-rbd
+resources:
+  - drpc.yaml
+  - placement.yaml
+  - placement-decision.yaml

dr/discovered/deployment-rbd/placement-decision.yaml

@@ -0,0 +1,6 @@
+apiVersion: cluster.open-cluster-management.io/v1beta1
+kind: PlacementDecision
+metadata:
+  labels:
+    cluster.open-cluster-management.io/placement: deployment-rbd-placement
+  name: placement-decision

dr/discovered/deployment-rbd/placement.yaml

@@ -0,0 +1,11 @@
+---
+apiVersion: cluster.open-cluster-management.io/v1beta1
+kind: Placement
+metadata:
+  annotations:
+    cluster.open-cluster-management.io/experimental-scheduling-disable: "true"
+  name: placement
+spec:
+  clusterSets:
+    - default
+  numberOfClusters: 1

dr/discovered/ramen-ops/binding.yaml

@@ -0,0 +1,8 @@
+---
+apiVersion: cluster.open-cluster-management.io/v1beta2
+kind: ManagedClusterSetBinding
+metadata:
+  name: default
+  namespace: ramen-ops
+spec:
+  clusterSet: default

workloads/kubevirt/README.md

@@ -24,7 +24,7 @@ the included SSH public key with your own public key.
 1. If you are not using the `main` branch update
    `subscription/base/subscription.yaml` to point to the right branch.
 
-## Deploying the VM subscription
+## Deploying an OCM managed VM
 
 To start a PVC based VM `vm-pvc` use the
 `subscription/kubevirt/vm-pvc-k8s-regional` overlay:
@@ -89,7 +89,7 @@ NAME                                          PROVISIONED  USED
 csi-vol-a3fdb384-2e31-49f1-bd48-a97b2d79f981      128 MiB  80 MiB
 ```
 
-## Enabling DR for the VM
+## Enabling DR for an OCM managed VM
 
 To allow *Ramen* to protect the VM, you need to disable *OCM*
 scheduling by adding an annotation to the VM placement:
@@ -104,7 +104,7 @@ kubectl annotate placement placement \
 Deploy the DR resources to enable DR:
 
 ```sh
-kubectl apply -k dr/kubevirt/vm-pvc-k8s-regional --context hub
+kubectl apply -k dr/managed/kubevirt/vm-pvc-k8s-regional --context hub
 ```
 
 At this point *Ramen* controls the VM placement and protects the VM data
@@ -209,7 +209,7 @@ csi-vol-a3fdb384-2e31-49f1-bd48-a97b2d79f981      128 MiB  80 MiB
 In case of a disaster in the primary cluster, we can start the VM using
 the replica on the secondary cluster.
 
-## Failing over to another cluster
+## Failing over an OCM managed VM to another cluster
 
 In case of disaster you can force the VM to run on the other cluster.
 The VM will start on the other cluster using the data from the last
@@ -351,12 +351,12 @@ kubectl wait drpc drpc \
     --context hub
 ```
 
-## Disable DR for the VM
+## Disable DR for an OCM managed VM
 
 Delete the `dr` resources to disable DR:
 
 ```sh
-kubectl delete -k dr/kubevirt/vm-pvc-k8s-regional --context hub
+kubectl delete -k dr/managed/kubevirt/vm-pvc-k8s-regional --context hub
 ```
 
 Enable *OCM* scheduling again by deleting the placement annotation we
@@ -372,7 +372,7 @@ kubectl annotate placement placement \
 At this point *OCM* controls the VM and the storage used for replicating
 the VM data on the DR clusters will be reclaimed.
 
-## Undeploying the VM
+## Undeploying an OCM managed VM
 
 Delete the subscription to stop and delete the VM: