Move channel into the subscription

Similar to ocm-ramen-sample PR[1] move the channel into the subscription
kustomization.

This is better for users, removing setup and teardown from the
deployment steps.  Now it is not possible to forget to deploy or remove
the channel after testing.

This is better for developers, since now we can test multiple VMs
concurrently, without dealing with setup and cleanup of shared
resources, since VMs do not share the channel.

[1] RamenDR/ocm-ramen-samples#41

Author: nirs

README.md

@@ -45,14 +45,6 @@ the included SSH public key with your own public key.
 1. If you are not using the `main` branch update
    `subscription/subscription.yaml` to point to the right branch.
 
-### Deploying the channel
-
-Deploy the channel to introduce this repo to *OCM*:
-
-```sh
-kubectl apply -k channel --context hub
-```
-
 ### Deploying the VM subscription
 
 To start the VM deploy the subscription:
@@ -408,11 +400,3 @@ Delete the subscription to stop and delete the VM:
 ```sh
 kubectl delete -k subscription --context hub
 ```
-
-### Delete the channel
-
-When done you can delete the channel:
-
-```sh
-kubectl delete -k channel --context hub
-```

channel/kustomization.yaml

@@ -2,7 +2,7 @@
 apiVersion: apps.open-cluster-management.io/v1
 kind: Channel
 metadata:
-  name: kubevirt-gitops
+  name: ocm-kubevirt-samples
 spec:
   type: GitHub
   pathname: https://github.com/aglitke/ocm-kubevirt-samples.git

channel/namespace.yaml

@@ -1,6 +1,7 @@
 ---
 resources:
 - namespace.yaml
+- channel.yaml
 - binding.yaml
 - placement.yaml
 - subscription.yaml

channel/channel.yaml subscription/channel.yamlchannel/channel.yaml renamed to subscription/channel.yaml

@@ -7,7 +7,7 @@ metadata:
     apps.open-cluster-management.io/github-path: vm-standalone-pvc-k8s
   name: kubevirt-sub
 spec:
-    channel: kubevirt-samples/kubevirt-gitops
+    channel: kubevirt-sample/ocm-kubevirt-samples
     placement:
       placementRef:
         kind: Placement