Installing RKE2 air-gapped is failed on helm

[rupang790]

Environmental Info:
RKE2 Version: v1.25.9+rke2r1

Node(s) CPU architecture, OS, and Version: Linux rancher01 3.10.0-1160.88.1.el7.x86_64 #1 SMP Tue Mar 7 15:41:52 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Cluster Configuration: Single node

Describe the bug:

I tried to install RKE2 air-gapped with harbor private registry.
When I use rke2 cli with system-default-registry flag, It looks fine to pull all images that mirrored.
$ rke2 server --system-default-registry [REGISTRY_NAME]:[PORT]

But, after that, there were error with helm-controller as below:

ERRO[0021] error syncing 'kube-system/rke2-coredns': handler helm-controller-chart-registration: helmcharts.helm.cattle.io "rke2-coredns" not found, requeuing
I0510 17:23:25.479255    4434 event.go:294] "Event occurred" object="kube-system/rke2-coredns" fieldPath="" kind="HelmChart" apiVersion="helm.cattle.io/v1" type="Normal" reason="ApplyJob" message="Applying HelmChart using Job kube-system/helm-install-rke2-coredns"
I0510 17:23:25.548835    4434 event.go:294] "Event occurred" object="kube-system/rke2-ingress-nginx" fieldPath="" kind="Addon" apiVersion="k3s.cattle.io/v1" type="Normal" reason="ApplyingManifest" message="Applying manifest at \"/var/lib/rancher/rke2/server/manifests/rke2-ingress-nginx.yaml\""
I0510 17:23:25.575137    4434 event.go:294] "Event occurred" object="kube-system/rke2-ingress-nginx" fieldPath="" kind="Addon" apiVersion="k3s.cattle.io/v1" type="Normal" reason="AppliedManifest" message="Applied manifest at \"/var/lib/rancher/rke2/server/manifests/rke2-ingress-nginx.yaml\""
ERRO[0021] error syncing 'kube-system/rke2-calico': handler helm-controller-chart-registration: helmcharts.helm.cattle.io "rke2-calico" not found, requeuing
I0510 17:23:25.679819    4434 event.go:294] "Event occurred" object="kube-system/rke2-calico" fieldPath="" kind="HelmChart" apiVersion="helm.cattle.io/v1" type="Normal" reason="ApplyJob" message="Applying HelmChart using Job kube-system/helm-install-rke2-calico"
I0510 17:23:25.946746    4434 event.go:294] "Event occurred" object="kube-system/rke2-metrics-server" fieldPath="" kind="Addon" apiVersion="k3s.cattle.io/v1" type="Normal" reason="ApplyingManifest" message="Applying manifest at \"/var/lib/rancher/rke2/server/manifests/rke2-metrics-server.yaml\""
INFO[0021] Running kube-proxy --cluster-cidr=10.42.0.0/16 --conntrack-max-per-core=0 --conntrack-tcp-timeout-close-wait=0s --conntrack-tcp-timeout-established=0s --healthz-bind-address=127.0.0.1 --hostname-override=rancher01 --kubeconfig=/var/lib/rancher/rke2/agent/kubeproxy.kubeconfig --proxy-mode=iptables
I0510 17:23:25.957262    4434 event.go:294] "Event occurred" object="kube-system/rke2-metrics-server" fieldPath="" kind="Addon" apiVersion="k3s.cattle.io/v1" type="Normal" reason="AppliedManifest" message="Applied manifest at \"/var/lib/rancher/rke2/server/manifests/rke2-metrics-server.yaml\""
I0510 17:23:26.346253    4434 event.go:294] "Event occurred" object="kube-system/rke2-multus" fieldPath="" kind="Addon" apiVersion="k3s.cattle.io/v1" type="Normal" reason="ApplyingManifest" message="Applying manifest at \"/var/lib/rancher/rke2/server/manifests/rke2-multus.yaml\""
INFO[0021] Starting /v1, Kind=Secret controller
I0510 17:23:26.358128    4434 event.go:294] "Event occurred" object="kube-system/rke2-multus" fieldPath="" kind="Addon" apiVersion="k3s.cattle.io/v1" type="Normal" reason="AppliedManifest" message="Applied manifest at \"/var/lib/rancher/rke2/server/manifests/rke2-multus.yaml\""
INFO[0022] Labels and annotations have been set successfully on node: rancher01
ERRO[0022] error syncing 'kube-system/rke2-calico-crd': handler helm-controller-chart-registration: helmcharts.helm.cattle.io "rke2-calico-crd" not found, requeuing
INFO[0022] Updating TLS secret for kube-system/rke2-serving (count: 10): map[listener.cattle.io/cn-10.43.0.1:10.43.0.1 listener.cattle.io/cn-127.0.0.1:127.0.0.1 listener.cattle.io/cn-192.168.6.144:192.168.6.144 listener.cattle.io/cn-__1-f16284:::1 listener.cattle.io/cn-kubernetes:kubernetes listener.cattle.io/cn-kubernetes.default:kubernetes.default listener.cattle.io/cn-kubernetes.default.svc:kubernetes.default.svc listener.cattle.io/cn-kubernetes.default.svc.cluster.local:kubernetes.default.svc.cluster.local listener.cattle.io/cn-localhost:localhost listener.cattle.io/cn-rancher01:rancher01 listener.cattle.io/fingerprint:SHA1=B773F4EDF89DFB00BBB8FCB1CD7277128E324F96]
I0510 17:23:26.746306    4434 event.go:294] "Event occurred" object="kube-system/rke2-snapshot-controller-crd" fieldPath="" kind="Addon" apiVersion="k3s.cattle.io/v1" type="Normal" reason="ApplyingManifest" message="Applying manifest at \"/var/lib/rancher/rke2/server/manifests/rke2-snapshot-controller-crd.yaml\""
I0510 17:23:26.759555    4434 event.go:294] "Event occurred" object="kube-system/rke2-snapshot-controller-crd" fieldPath="" kind="Addon" apiVersion="k3s.cattle.io/v1" type="Normal" reason="AppliedManifest" message="Applied manifest at \"/var/lib/rancher/rke2/server/manifests/rke2-snapshot-controller-crd.yaml\""

For this, what should I prepare or configure to solve?
I search on google and rke2 document page, there were no information about this.
Please help us.

Steps To Reproduce:

• Installed RKE2:

Expected behavior:

Actual behavior:

Additional context / logs:

[brandond]

These messages are normal when the helm controller is starting up and the caches have not yet been populated. They have nothing to do with image pulls or registries. If there is something wrong with your cluster that is preventing it from working, it is not related to any of the log messages you've shared here.