Add missing label for the custom HelmRepository

Closes k0rdent/kcm#854

docs/admin-service-templates.md

@@ -8,14 +8,16 @@ and use it to deploy an application to a k0rdent child cluster.
 
 The basic sequence looks like this:
 
-  1. Define the source of the Helm chart that defines the service.  For example, this YAML describes a custom `Source` object of `kind` `HelmRepository`:
+  1. Define the source of the Helm chart that defines the service. The source object must have the label `k0rdent.mirantis.com/managed: "true"`. For example, this YAML describes a custom `Source` object of `kind` `HelmRepository`:
 
     ```yaml
     apiVersion: source.toolkit.fluxcd.io/v1
     kind: HelmRepository
     metadata:
       name: custom-templates-repo
       namespace: kcm-system
+      labels:
+        k0rdent.mirantis.com/managed: "true"
     spec:
       insecure: true
       interval: 10m0s
@@ -113,4 +115,4 @@ The basic sequence looks like this:
     ```shell
     kubectl patch clusterdeployment my-managed-cluster -n my-target-namespace --type='merge' -p '{"spec":{"services":[{"template":"project-ingress-nginx-4.11.3","name":"ingress-nginx","namespace":"my-target-namespace"}]}}'
     ```
-    For more information on creating and using `ServiceTemplate` objects, see the [User Guide](user-create-service.md).
+    For more information on creating and using `ServiceTemplate` objects, see the [User Guide](user-create-service.md).

docs/template-byo.md

@@ -19,12 +19,18 @@ Note that it's important to pay attention to where the source resides. Cluster-s
 
 For example, this YAML describes a custom `Source` object of `kind` `HelmRepository`:
 
+> NOTE:
+> The custom `HelmRepository` must have the label
+> `k0rdent.mirantis.com/managed: "true"`.
+
 ```yaml
 apiVersion: source.toolkit.fluxcd.io/v1
 kind: HelmRepository
 metadata:
   name: k0rdent-templates
   namespace: kcm-system
+  labels:
+    k0rdent.mirantis.com/managed: "true"
 spec:
   insecure: true
   interval: 10m0s