adamant-kite-43734
02/26/2025, 4:45 PMhundreds-evening-84071
02/26/2025, 5:20 PMeager-needle-79094
02/27/2025, 8:24 AMhelm install rancher rancher-stable/rancher --create-namespace --namespace cattle-system --set tls=external --set hostname=mysslproxybalancer.mydomain.com --set bootstrapPassword=admin --set-json 'extraNodeSelectorTerms=[{ "key": "node-role.kubernetes.io/master", "operator": "Exists"}]' --set 'service.type=NodePort' --set debug=true --set replicas=1 --set startupProbe.timeoutSeconds=120
(only 1 replica just hoping to avoid any possibile inter-node communication issue)
and the whole pod log contained the following ERROR lines
2025/02/26 14:53:41 [ERROR] failed to start cluster controllers local: context canceled
2025/02/26 14:53:41 [ERROR] Failed to find system chart fleet will try again in 5 seconds: configmaps "" not found
2025/02/26 14:53:42 [ERROR] error syncing 'fleet-local/local': handler cluster-create: server url is missing, can't generate kubeconfig for fleet import cluster, requeuing
2025/02/26 14:53:42 [ERROR] error syncing 'fleet-local/local': handler cluster-create: server url is missing, can't generate kubeconfig for fleet import cluster, requeuing
2025/02/26 14:53:42 [ERROR] error syncing 'fleet-local/local': handler cluster-create: server url is missing, can't generate kubeconfig for fleet import cluster, requeuing
2025/02/26 14:53:43 [ERROR] error syncing 'fleet-local/local': handler cluster-create: server url is missing, can't generate kubeconfig for fleet import cluster, requeuing
(where only now I'm realizing that maybe "_failed to start cluster controllers local: context canceled_" deserves more attention than any subsequent fleet-related issue)
After a while (non service comes up and startup probe fails), the pod gives up:
Back-off restarting failed container rancher in pod rancher-...