![]() ![]() Pulling images required for setting up a Kubernetes cluster : firewalld is active, please ensure ports are open or your cluster may not function correctly Kube-system kube-scheduler-node0 1/1 Running 0 11h Kube-system kube-proxy-qflcw 1/1 Running 0 11h Kube-system kube-proxy-jh26p 1/1 Running 0 11h Kube-system kube-proxy-glh92 1/1 Running 0 11h Kube-system kube-proxy-dlhc7 1/1 Running 0 11h Kube-system kube-flannel-ds-arm-q8t5k 1/1 Running 0 11h Kube-system kube-flannel-ds-arm-fwzkl 1/1 Running 0 11h ![]() Kube-system kube-flannel-ds-arm-dcprj 1/1 Running 0 11h Kube-system kube-flannel-ds-arm-4zq4g 1/1 Running 0 11h Kube-system kube-controller-manager-node0 1/1 Running 0 11h ![]() ![]() Kube-system kube-apiserver-node0 1/1 Running 0 11h Kube-system coredns-f9fd979d6-xl5f2 1/1 Running 0 11h Kube-system coredns-f9fd979d6-jjsjr 1/1 Running 0 11h The connection to the server localhost:8080 was refused - did you specify the right host or $ kubectl get pods -all-namespaces You can see the difference between the working “pi” users and the “root” user who does not have the config file: $ sudo kubectl get pods -all-namespaces For me that was a user that had the nf file copied to ~/.kube/config. Yes I had to be sure I used the “right user”. stop the firewalld but still got the same error. I have added the IP address+port to the iptables, tried again. When it comes to “kubectl get nodes” I receive the error: The connection to the server x.x.x.x:6443 was refused - did you specify the right host or port? But cannot telnet into any of the machines from my physical Windows machine. I can ssh from master to host and visa-verse. I got docker installed to the host and kubectl installed to master. I am running two nodes, one master and the other host.īoth are VMs running CentOS in Oracle Virtual Manager. I have currently started working on this as well and I am running into the same brickwall. And if you can’t fix it, please report back with the steps you did, why it failed (the error) and what you tried and didn’t work. If it does fail, try to fix that instead of continuing with the next steps. If I were you, I’d try removing everything from a previous run and starting from scratch and making sure nothing fails. That is the way to authorize to the cluster, so it won’t never work if that step doesn’t work So, either an old file from a previous installation is there or something silly like that (although usually difficult to spot).Īlso, make sure the commands don’t fail (some on the post pasted that the step to copy the kubectl config failed). Basically, if you install and have a proper config file, it should always work. Getting kubectl to run really depends on how you installed it. > else sudo sed -i "s/127.0.0.1 localhost/127.0.0.This seems like another way to setup the cluster that said on the post ( ). This is the result of using sudo fresh out of the box.īelow, the hostname is missing in /etc/hosts, which results in the error in the command that is made to fix it, which we can then see sudo no longer results in afterwards. The install is aware of the hostname, but in my case didn't get set in /etc/hosts for localhost, sudo calls made on the system result in hostname resolution errors. I didn't see it on the issues here in a search or perusing the pages, sorry if it's a duplicate. It should be possible to add an extra command post install if detected. Fairly simple issue here, possibly an upstream bug due to the image used, as appears to be reported in a few different ubuntu images. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |