![]() 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. ![]() You can also retrieve the host's ip address from within a docker container depending on your OS and docker version:Īs of Docker v18.03+ you can use the hostname to connect to your Docker host.This seems like another way to setup the cluster that said on the post ( ). localhost:8080 However you need to remember that ports are a scarce resource and you cannot have conflicting port listeners in different containers when you do this. This should allow you to access the host machine via listening port of the host machine. service1:80 -> host:8080, service2:80 -> host:8081).ĭocker run YOUR_IMAGE -network="host" will bind the container network adapter to that of the host machine. 80), but in a way that can be mapped to unique ports on the host machine (e.g. This allows one to easily spin up multiple containers which might all listen on the same port (e.g. usr/bin/docker daemon -H fd://ĭocker container can reach DNS but not resolve hostsīy default creating a new docker container also creates a virtual network that separates the docker network environment from the host network environment (somewhat). From my host I can ping google $ cat /etc/nf
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |