title: Rancher's helm-operations fail
body: <p>I've installed fresh rancher on microk8s using helm3 and there are helm operations failing periodically. I am rather clueless as where to have a look for what. Could you please point me in the right direction?</p>
  <pre><code>Waiting for Kubernetes API to be available
  helm upgrade --history-max=5 --install=true --namespace=rancher-operator-system --reset-values=true --timeout=5m0s --values=/home/shell/helm/values-rancher-operator-crd-0.1.100.yaml --version=0.1.100 --wait=true rancher-operator-crd /home/shell/helm/rancher-operator-crd-0.1.100.tgz
  Release &quot;rancher-operator-crd&quot; does not exist. Installing it now.
  W1129 15:37:01.028852      39 warnings.go:67] apiextensions.k8s.io/v1beta1 CustomResourceDefinition is deprecated in v1.16+, unavailable in v1.22+; use apiextensions.k8s.io/v1 CustomResourceDefinition
  Error: rendered manifests contain a resource that already exists. Unable to continue with install: CustomResourceDefinition &quot;clusters.rancher.cattle.io&quot; in namespace &quot;&quot; exists and cannot be imported into the current release: invalid ownership metadata; label validation error: missing key &quot;app.kubernetes.io/managed-by&quot;: must be set to &quot;Helm&quot;; annotation validation error: missing key &quot;meta.helm.sh/release-name&quot;: must be set to &quot;rancher-operator-crd&quot;; annotation validation error: missing key &quot;meta.helm.sh/release-namespace&quot;: must be set to &quot;rancher-operator-system&quot;
  </code></pre>
  <pre><code>Waiting for Kubernetes API to be available
  helm upgrade --history-max=5 --install=true --namespace=fleet-system --reset-values=true --timeout=5m0s --version=0.3.100 --wait=true fleet-crd /home/shell/helm/fleet-crd-0.3.100.tgz
  Release &quot;fleet-crd&quot; does not exist. Installing it now.
  W1129 15:36:48.667489      41 warnings.go:67] apiextensions.k8s.io/v1beta1 CustomResourceDefinition is deprecated in v1.16+, unavailable in v1.22+; use apiextensions.k8s.io/v1 CustomResourceDefinition
  Error: rendered manifests contain a resource that already exists. Unable to continue with install: CustomResourceDefinition &quot;bundles.fleet.cattle.io&quot; in namespace &quot;&quot; exists and cannot be imported into the current release: invalid ownership metadata; label validation error: missing key &quot;app.kubernetes.io/managed-by&quot;: must be set to &quot;Helm&quot;; annotation validation error: missing key &quot;meta.helm.sh/release-name&quot;: must be set to &quot;fleet-crd&quot;; annotation validation error: missing key &quot;meta.helm.sh/release-namespace&quot;: must be set to &quot;fleet-system&quot;
  </code></pre>
  <p>maybe the problem is I installed it with helm3? I would like to use the latest technology, so I would like to use helm3. Is that possible? If not, is it possible to use both helms side by side?</p>