Hi,
I have following setup:
Windows 10 machine I host Rancher v2.5.17 on (requirement to the OS and version)
5x RPi 4 B with Ubuntu 22.04 LTS 64-bit OS, hosting k3s cluster
I want to import the cluster to Rancher. K3s installation works fine, but I'm struggling to install rancher/rancher-agent:v2.5.17-linux-arm64 and import the cluster to Rancher.
I do the following:
• Modify win firewall to accept inbound TCP connections on ports 8080 and 8443
• install rancher with:
◦ docker run --privileged -d --restart=always -p 8080:80 -p 8443:443 rancher/rancher:v2.5.17
• paste generated command to pull yaml file and apply it on the controller node
• in the cluster API I set "agentImageOverride" to ARM64 image: rancher/rancher-agent:v2.5.17-linux-arm64
Result:
• cluster in Rancher is kept in the "Pending" state
• cattle agent pod doesn't get to ready state and keeps restarting and failing
• running following command:
◦ kubectl describe pod [cattle cluster agent pod] -n cattle-system
• gives me the output:
◦ Events:
◦ Type Reason Age From Message
◦ ---- ------ ---- ---- -------
◦ Normal Scheduled 9m29s default-scheduler Successfully assigned cattle-system/cattle-cluster-agent-c4d59f4cb-slmmk to rpi3
◦ Normal Pulling 9m29s kubelet Pulling image "rancher/rancher-agent:v2.5.17-linux-arm64"
◦ Normal Pulled 4m56s kubelet Successfully pulled image "rancher/rancher-agent:v2.5.17-linux-arm64" in 4m33.244685709s
◦ Normal Created 4m56s kubelet Created container cluster-register
◦ Normal Started 4m55s kubelet Started container cluster-register
◦ Warning Unhealthy 3m19s (x22 over 4m53s) kubelet Readiness probe failed: Get "http://10.42.0.14:8080/health": dial tcp 10.42.0.14:8080: connect: connection refused
Does anyone know why the connection gets refused and how to workaround it? Any help highly appreciated.
Thanks!
Oskar
b
big-hydrogen-97240
01/26/2023, 11:22 AM
You shouldn't have to modify the agent image tag. It will work as-is.
Are there any abnormal logs in from the Rancher agent pods?
m
magnificent-jackal-25711
01/26/2023, 6:04 PM
In logs it was about missing secret/CA certs. But actually the information I don't have to modify the image tag for ARM lead me step by step to working import. So thank you a lot for this hint!