in the jobs rke-user-addon-deployment i have this (very strange)
┌─────────────────────────────────────────────────────────────────────────────────────────── Logs(kube-system/rke-user-addon-deploy-job-g9rnr:rke-user-addon-pod)[tail] ───────────────────────────────────────────────────────────────────────────────────────────┐
│ Autoscroll:On FullScreen:Off Timestamps:Off Wrap:Off │
│ error: You must be logged in to the server (the server has asked for the client to provide credentials) │
│ Stream closed EOF for kube-system/rke-user-addon-deploy-job-g9rnr (rke-user-addon-pod) │
and in the metrics server i have this
│ E0415 14:51:31.215141 1 scraper.go:140] "Failed to scrape node" err="Get \"https://192.168.137.42:10250/metrics/resource\": dial tcp 192.168.137.42:10250: connect: no route to host" node="master2" │
│ E0415 14:51:33.263196 1 scraper.go:140] "Failed to scrape node" err="Get \"https://192.168.137.63:10250/metrics/resource\": dial tcp 192.168.137.63:10250: connect: no route to host" node="worker3" │
│ E0415 14:51:33.263195 1 scraper.go:140] "Failed to scrape node" err="Get \"https://192.168.137.65:10250/metrics/resource\": dial tcp 192.168.137.65:10250: connect: no route to host" node="worker5" │
│ E0415 14:51:37.295226 1 scraper.go:140] "Failed to scrape node" err="Get \"https://192.168.137.41:10250/metrics/resource\": dial tcp 192.168.137.41:10250: connect: no route to host" node="master1" │
│ E0415 14:51:37.295302 1 scraper.go:140] "Failed to scrape node" err="Get \"https://192.168.137.64:10250/metrics/resource\": dial tcp 192.168.137.64:10250: connect: no route to host" node="worker4" │
│ E0415 14:51:37.359145 1 scraper.go:140] "Failed to scrape node" err="Get \"https://192.168.137.43:10250/metrics/resource\": dial tcp 192.168.137.43:10250: connect: no route to host" node="master3" │
│ E0415 14:51:37.359151 1 scraper.go:140] "Failed to scrape node" err="Get \"https://192.168.137.61:10250/metrics/resource\": dial tcp 192.168.137.61:10250: connect: no route to host" node="worker1" │
│ E0415 14:51:46.191171 1 scraper.go:140] "Failed to scrape node" err="Get \"https://192.168.137.43:10250/metrics/resource\": dial tcp 192.168.137.43:10250: connect: no route to host" node="master3" │
│ E0415 14:51:48.239178 1 scraper.go:140] "Failed to scrape node" err="Get \"https://192.168.137.63:10250/metrics/resource\": dial tcp 192.168.137.63:10250: connect: no route to host" node="worker3" │
│ E0415 14:51:48.239298 1 scraper.go:140] "Failed to scrape node" err="Get \"https://192.168.137.42:10250/metrics/resource\": dial tcp 192.168.137.42:10250: connect: no route to host" node="master2" │
│ E0415 14:51:52.335177 1 scraper.go:140] "Failed to scrape node" err="Get \"https://192.168.137.64:10250/metrics/resource\": dial tcp 192.168.137.64:10250: connect: no route to host" node="worker4" │
`
``
We found the problem; it was the firewall blocking the traffic on the port. Also, I respected the documentation, but maybe the doc needs an update? Currently, I will just disable the firewall.
RKE version: While running the rke setup we have this problem (@athomsAF)
Moreover, we also have the followings pods showing an error (sometimes) and if here is the error we can't see the logs:
rke version v1.5.6
Docker version: (
docker version
,docker info
preferred)docker version
docker info
Operating system and kernel: (
cat /etc/os-release
,uname -r
preferred)Type/provider of hosts: (VirtualBox/Bare-metal/AWS/GCE/DO)
Bare-metal
cluster.yml file:
Steps to Reproduce:
To do in the terminal
rm -rf ~/.kube/config rke remove --config ./cluster.yml --force rke up --config ./cluster.yml cp kube_config_cluster.yml ~/.kube/config k9s
Results: In k9s I get this
in the jobs rke-user-addon-deployment i have this (very strange)
and in the metrics server i have this