Helm install pods failing after rke1 to rke2 migration

[dnoland1]

1. Using Rancher v2.6.3, created a one node (worker/cp/etcd) v1.21.10 cluster using all default options, except etcd snapshots to s3 bucket.
2. Followed directions at https://docs.rke2.io/migration/

Pods after migration:

ip-10-0-98-10:~ # kubectl get pods -A
NAMESPACE             NAME                                        READY   STATUS             RESTARTS        AGE
cattle-fleet-system   fleet-agent-8fcfb99b6-hbcsp                 1/1     Running            1               21m
cattle-system         cattle-cluster-agent-59b57bcdf9-vd5ft       1/1     Running            3               22m
cattle-system         cattle-node-agent-5cb7b                     1/1     Running            1               22m
cattle-system         kube-api-auth-jfwgc                         1/1     Running            1               22m
ingress-nginx         ingress-nginx-admission-create-4vvm6        0/1     Completed          0               22m
ingress-nginx         ingress-nginx-admission-patch-bh8ml         0/1     Completed          0               22m
ingress-nginx         nginx-ingress-controller-4b52n              1/1     Running            1               22m
kube-system           calico-kube-controllers-6c977d77bc-n7m2x    1/1     Running            1               22m
kube-system           canal-99sf4                                 2/2     Running            2               22m
kube-system           cloud-controller-manager-ip-10-0-98-10      1/1     Running            0               12m
kube-system           coredns-685d6d555d-csfwc                    1/1     Running            1               22m
kube-system           coredns-autoscaler-96789f8f7-sgtfw          1/1     Running            1               22m
kube-system           etcd-ip-10-0-98-10                          1/1     Running            0               12m
kube-system           helm-install-rke2-canal--1-b9s2p            0/1     CrashLoopBackOff   6 (5m2s ago)    12m
kube-system           helm-install-rke2-coredns--1-x67d6          0/1     CrashLoopBackOff   6 (4m57s ago)   12m
kube-system           helm-install-rke2-ingress-nginx--1-6gn2v    0/1     Error              7 (5m15s ago)   12m
kube-system           helm-install-rke2-metrics-server--1-5s6f8   0/1     CrashLoopBackOff   6 (5m1s ago)    12m
kube-system           kube-apiserver-ip-10-0-98-10                1/1     Running            0               12m
kube-system           kube-controller-manager-ip-10-0-98-10       1/1     Running            0               12m
kube-system           kube-proxy-ip-10-0-98-10                    1/1     Running            0               12m
kube-system           kube-scheduler-ip-10-0-98-10                1/1     Running            0               12m
kube-system           metrics-server-7bf4b68b78-hm9b6             1/1     Running            1               22m
kube-system           rke-coredns-addon-deploy-job-mpg82          0/1     Completed          0               22m
kube-system           rke-ingress-controller-deploy-job-n4nzq     0/1     Completed          0               22m
kube-system           rke-metrics-addon-deploy-job-wjx8j          0/1     Completed          0               22m
kube-system           rke-network-plugin-deploy-job-2hdsj         0/1     Completed          0               22m

End of logs:

ip-10-0-98-10:~ # kubectl logs -n kube-system helm-install-rke2-canal--1-b9s2p --tail=3
+ helm_v3 install --set-string global.clusterCIDR=10.42.0.0/16 --set-string global.clusterCIDRv4=10.42.0.0/16 --set-string global.clusterCIDRv6= --set-string global.clusterDNS=10.43.0.10 --set-string global.clusterDomain=cluster.local --set-string global.rke2DataDir=/var/lib/rancher/rke2 --set-string global.serviceCIDR=10.43.0.0/16 --set-string global.systemDefaultRegistry= rke2-canal /tmp/rke2-canal.tgz --values /config/values-10_HelmChartConfig.yaml
Error: rendered manifests contain a resource that already exists. Unable to continue with install: ServiceAccount "canal" in namespace "kube-system" exists and cannot be imported into the current release: invalid ownership metadata; label validation error: missing key "app.kubernetes.io/managed-by": must be set to "Helm"; annotation validation error: missing key "meta.helm.sh/release-name": must be set to "rke2-canal"; annotation validation error: missing key "meta.helm.sh/release-namespace": must be set to "kube-system"
+ exit

ip-10-0-98-10:~ # kubectl logs -n kube-system  helm-install-rke2-coredns--1-x67d6 --tail=3
+ helm_v3 install --set-string global.clusterCIDR=10.42.0.0/16 --set-string global.clusterCIDRv4=10.42.0.0/16 --set-string global.clusterCIDRv6= --set-string global.clusterDNS=10.43.0.10 --set-string global.clusterDomain=cluster.local --set-string global.rke2DataDir=/var/lib/rancher/rke2 --set-string global.serviceCIDR=10.43.0.0/16 --set-string global.systemDefaultRegistry= rke2-coredns /tmp/rke2-coredns.tgz --values /config/values-10_HelmChartConfig.yaml
Error: rendered manifests contain a resource that already exists. Unable to continue with install: ServiceAccount "coredns" in namespace "kube-system" exists and cannot be imported into the current release: invalid ownership metadata; label validation error: missing key "app.kubernetes.io/managed-by": must be set to "Helm"; annotation validation error: missing key "meta.helm.sh/release-name": must be set to "rke2-coredns"; annotation validation error: missing key "meta.helm.sh/release-namespace": must be set to "kube-system"
+ exit

ip-10-0-98-10:~ # kubectl logs -n kube-system helm-install-rke2-ingress-nginx--1-6gn2v --tail=3
+ helm_v3 install --set-string global.clusterCIDR=10.42.0.0/16 --set-string global.clusterCIDRv4=10.42.0.0/16 --set-string global.clusterCIDRv6= --set-string global.clusterDNS=10.43.0.10 --set-string global.clusterDomain=cluster.local --set-string global.rke2DataDir=/var/lib/rancher/rke2 --set-string global.serviceCIDR=10.43.0.0/16 --set-string global.systemDefaultRegistry= rke2-ingress-nginx /tmp/rke2-ingress-nginx.tgz --values /config/values-10_HelmChartConfig.yaml
Error: rendered manifests contain a resource that already exists. Unable to continue with install: IngressClass "nginx" in namespace "" exists and cannot be imported into the current release: invalid ownership metadata; label validation error: missing key "app.kubernetes.io/managed-by": must be set to "Helm"; annotation validation error: missing key "meta.helm.sh/release-name": must be set to "rke2-ingress-nginx"; annotation validation error: missing key "meta.helm.sh/release-namespace": must be set to "kube-system"
+ exit

ip-10-0-98-10:~ # kubectl logs -n kube-system helm-install-rke2-metrics-server--1-5s6f8 --tail=3
+ helm_v3 install --set-string global.clusterCIDR=10.42.0.0/16 --set-string global.clusterCIDRv4=10.42.0.0/16 --set-string global.clusterCIDRv6= --set-string global.clusterDNS=10.43.0.10 --set-string global.clusterDomain=cluster.local --set-string global.rke2DataDir=/var/lib/rancher/rke2 --set-string global.serviceCIDR=10.43.0.0/16 --set-string global.systemDefaultRegistry= rke2-metrics-server /tmp/rke2-metrics-server.tgz --values /config/values-10_HelmChartConfig.yaml
Error: rendered manifests contain a resource that already exists. Unable to continue with install: APIService "v1beta1.metrics.k8s.io" in namespace "" exists and cannot be imported into the current release: invalid ownership metadata; label validation error: missing key "app.kubernetes.io/managed-by": must be set to "Helm"; annotation validation error: missing key "meta.helm.sh/release-name": must be set to "rke2-metrics-server"; annotation validation error: missing key "meta.helm.sh/release-namespace": must be set to "kube-system"
+ exit