Unable to join master node

When I try to join to the master node from the worker node i get the following error when i type the command:
I get:
Both the hash for the ca.crt certificate and the token are correct,doing a ping against the master ip and k8smaster dns name returns correct answers, could you help me with this issue?
Thanks in advance
Comments
-
Hi @suarna,
It seems that the join has trouble resolving the "k8smaster" alias. Edit the
/etc/hosts
of the worker and ensure that the correct alias is used, and the private IP of the master is used as well.Also, keep in mind that running the join command several times will cause more errors that help. In between joins I would recommend running a
sudo kubeadm reset
.Regards,
-Chris0 -
Hello,
Please also include the exact kubeadm init command you used on the master along with the contents of the kubeadm-config.yaml file.
Regards,
0 -
Looking in dept i saw the problem. I am using two VM's in one of them i deploy the master node and in the other the worker node, i have two network devices on each of it,one device connected via NAT through the host system to the outside world and the other devices connected both to the same internal network. I want to start the service listening on the device of the internal network instead of the NATed device,but i do not know why the service is created on the other device despite the content of the config file.
The init command used is:
The ip 192.168.1.1 is conmected to the internal network,(this is device in which i want run the service)
Here you can see the kubeadm-config.yaml file content
And finally the admin.conf created when the master node is deployed,the service (and the certs) are created for the the ip 10.0.2.15 that correponds with the NATed device instead of the ip 192.168.1.1that corresponds with the device connected to the internal network, and in that way reflected in the hosts file and in the kubeadm-config.yaml file (in the image below I have intentionally ommited the certificates content)
In what way can i control in which device can I deploy the service running for the port 6443?
0 -
Hello,
Your pod subnet (using 192.168.x.y) should not be the same as the host network (k8smaster also being 192.168.x.y). It will cause issues with routing. If you read the lab exercise you will find in Exercise 3.1, step 9 and 10 to not use the same IP address.
Also the labs are tested with single interfaces, you may encounter other issues if you use a multi-interface configuration. You can read up on the use of --apiserver-advertise-address string setting to kubeadm
Regards,
0 -
Hi @suarna,
In addition, your
kubeadm-config.yaml
file seems to be improperly formatted. The last line with thepodSubnet: ...
entry should only be indented 2 (two) spaces from the left. Yours seems to be indented about 8 (eight) spaces, and that is something that will cause that property and its assigned value to be unrecognized by the yaml to json converter.Regards,
-Chris0 -
Thanks for the remark @chrispokorni, i will look close at that
0 -
Finally I was able to join the worker node with the master node,but the node shows the not ready state when I run the_ kubectl get nodes_ command
Running the command kubectl describe node worker the following error is shown,it seems that there is an issue with the network plugin
Looking at the pod i can see two containers stucked in the states Init:0/3 and Container Creating,if i delete them they automaticaly try to run again with the same result.
0 -
Hi,
To troubleshoot the problem pods, you could run the
kubectl describe
command and study theEvents
section of the output:kubectl -n kube-system describe pod kube-proxy-hkbbm
kubectl -n kube-system describe pod calico-node-9zfd6
Any meaningful clues?
Regards,
-Chris0 -
I have obtained the following warning...either the calico or the kube-proxy containers show the same.
0 -
It seems your worker cannot resolve the container registry address.
Can you compare the
/etc/resolv.conf
files of worker and master, and see what is missing from the worker resolv file?Regards,
-Chris0 -
Hello,
This issue seems tied to host networking, not Kubernetes. Did you make sure the pod network and the host network no longer overlap, both had been 192.168.x.y?
I note a previous error from docker said "network plugin is not ready". If you log into your worker VM and run sudo docker run hello-world what output do you see?
Are you using VirtualBox or some other tool to host your VMs? Do both VMs have a single interface or more than one?
Regards,
0 -
Hi
Know is working fine...I had an error in a netplan config file in the worker side, I was driving traffic to the incorrect gateway,i noticed the error executing the suggested docker command provided by @serevwick,when then i could see that docker wasn't able to download the image from the docker registry, many thanks to both.
0 -
Great! Glad you have it working. :-)
0
Categories
- All Categories
- 51 LFX Mentorship
- 104 LFX Mentorship: Linux Kernel
- 576 Linux Foundation IT Professional Programs
- 304 Cloud Engineer IT Professional Program
- 125 Advanced Cloud Engineer IT Professional Program
- 53 DevOps Engineer IT Professional Program
- 61 Cloud Native Developer IT Professional Program
- 5 Express Training Courses
- 5 Express Courses - Discussion Forum
- 2.1K Training Courses
- 19 LFC110 Class Forum
- 7 LFC131 Class Forum
- 27 LFD102 Class Forum
- 158 LFD103 Class Forum
- 20 LFD121 Class Forum
- 1 LFD137 Class Forum
- 61 LFD201 Class Forum
- 1 LFD210 Class Forum
- LFD210-CN Class Forum
- 1 LFD213 Class Forum - Discontinued
- 128 LFD232 Class Forum
- LFD237 Class Forum
- 23 LFD254 Class Forum
- 611 LFD259 Class Forum
- 105 LFD272 Class Forum
- 1 LFD272-JP クラス フォーラム
- 1 LFD273 Class Forum
- 2 LFS145 Class Forum
- 25 LFS200 Class Forum
- 739 LFS201 Class Forum
- 1 LFS201-JP クラス フォーラム
- 11 LFS203 Class Forum
- 75 LFS207 Class Forum
- 300 LFS211 Class Forum
- 54 LFS216 Class Forum
- 47 LFS241 Class Forum
- 41 LFS242 Class Forum
- 37 LFS243 Class Forum
- 11 LFS244 Class Forum
- 37 LFS250 Class Forum
- 1 LFS250-JP クラス フォーラム
- LFS251 Class Forum
- 141 LFS253 Class Forum
- LFS254 Class Forum
- 1.1K LFS258 Class Forum
- 10 LFS258-JP クラス フォーラム
- 93 LFS260 Class Forum
- 132 LFS261 Class Forum
- 33 LFS262 Class Forum
- 80 LFS263 Class Forum
- 15 LFS264 Class Forum
- 11 LFS266 Class Forum
- 18 LFS267 Class Forum
- 18 LFS268 Class Forum
- 23 LFS269 Class Forum
- 203 LFS272 Class Forum
- 1 LFS272-JP クラス フォーラム
- LFS274 Class Forum
- LFS281 Class Forum
- 236 LFW211 Class Forum
- 172 LFW212 Class Forum
- 7 SKF100 Class Forum
- SKF200 Class Forum
- 903 Hardware
- 219 Drivers
- 74 I/O Devices
- 44 Monitors
- 116 Multimedia
- 209 Networking
- 101 Printers & Scanners
- 85 Storage
- 763 Linux Distributions
- 88 Debian
- 66 Fedora
- 15 Linux Mint
- 13 Mageia
- 24 openSUSE
- 142 Red Hat Enterprise
- 33 Slackware
- 13 SUSE Enterprise
- 357 Ubuntu
- 479 Linux System Administration
- 41 Cloud Computing
- 70 Command Line/Scripting
- Github systems admin projects
- 95 Linux Security
- 78 Network Management
- 108 System Management
- 49 Web Management
- 68 Mobile Computing
- 23 Android
- 30 Development
- 1.2K New to Linux
- 1.1K Getting Started with Linux
- 538 Off Topic
- 131 Introductions
- 217 Small Talk
- 22 Study Material
- 826 Programming and Development
- 278 Kernel Development
- 514 Software Development
- 928 Software
- 260 Applications
- 184 Command Line
- 3 Compiling/Installing
- 76 Games
- 316 Installation
- 61 All In Program
- 61 All In Forum
Upcoming Training
-
August 20, 2018
Kubernetes Administration (LFS458)
-
August 20, 2018
Linux System Administration (LFS301)
-
August 27, 2018
Open Source Virtualization (LFS462)
-
August 27, 2018
Linux Kernel Debugging and Security (LFD440)