Kubeadm failed to join
I realise this might be the same issue with the other post with the same title, but the solution was updated firewall rules to allow all ports.
I already did that but this issue consist the same, I tried restart the VM but it didn't do anything. I don't mind to redo the whole thing but I wish to understand the issue here and hopefully this will help someone there is new like me.
Here is the spec for both cp and worker (e2-medium)
The screenshot of the error
The screenshot of the CP VM & Firewall settings
The screenshot of the VPC network
The screenshot of the Firewall on VPC network
Answers
-
Hi @jasonseah,
Thank you for providing infra and CLI details. While the VPC and firewall look ok, However, I am concerned about the hardware profile of your instances. e2-medium is a 2vCPU/4GB mem, and the video guide from Chapter 1 is calling for 2vCPU/8GB mem which would be an e2-standard-2. Sometimes Kubernetes components panic when they do not have enough resources.
Also, the worker VM should be on the same network as the cp VM, meaning in the same VPC, under the same firewall. This was not provided above, but it is worth mentioning as it may be another reason for initial failures.
Configuring multiple runtimes, as in both docker and cri-o, will also cause Kubernetes agents to panic. Please make sure you only use the recommended runtime for this course release - the docker runtime.
When bootstrapping the cluster, please follow the Kubernetes version found in the Chapter 3. A misconfiguration of the
docker/daemon.json
file may produce errors as well.The
/etc/hosts
files of both VMs are expected to include the private IP of the cp node and thek8scp
alias.Hope this helps to get the issues resolved.
Regards,
-Chris1 -
Hi @chrispokorni,
Thanks for the reply, and you have my thanks! It solve the problem but for the record if someone fell for the same mistake as I am I am going to write down what I went through.
for the VM instance, yes it was my mistake for using a smaller machine, but I do have a separate worker VM running the same VPC network as the CP, the reason I did not mention is is because since both are having the similar setting which created by "create similar button".
Configuring multiple runtimes is not the problem happen for me, both are using docker.
the
/etc/hosts
for both VMs are using the same private IP of the cp node and withk8scp
aliasFor bootstrapping the cluster, this is what cause the issue, when I pasted the configuration that I copied from the PDF, it was a one liner json, so I didn't think that much I just saved it and restart the docker so apparently one liner json won't work for this case, I have to retype it and restart the docker, then suddenly it works!
Thank you so much Chris! you have just made my day!
Regards,
- Jason Seah
0 -
Hi @jasonseah,
Glad it all works now!
However, keep in mind that you have the SOLUTIONS tarball, where most config files are available for you as
.yaml
,.sh
,.json
,.cfg
, etc... So there is no need to copy file content from the PDF - this process typically introduces formatting issues such as the one you reported above.Regards,
-Chris1 -
0
Categories
- 9.8K All Categories
- 26 LFX Mentorship
- 79 LFX Mentorship: Linux Kernel
- 438 Linux Foundation Boot Camps
- 260 Cloud Engineer Boot Camp
- 87 Advanced Cloud Engineer Boot Camp
- 40 DevOps Engineer Boot Camp
- 18 Cloud Native Developer Boot Camp
- Express Training Courses
- Express Courses - Discussion Forum
- 1.5K Training Courses
- 17 LFC110 Class Forum
- 3 LFC131 Class Forum
- 18 LFD102 Class Forum
- 113 LFD103 Class Forum
- 8 LFD121 Class Forum
- 59 LFD201 Class Forum
- 1 LFD213 Class Forum - Discontinued
- 128 LFD232 Class Forum
- 23 LFD254 Class Forum
- 529 LFD259 Class Forum
- 99 LFD272 Class Forum
- 1 LFD272-JP クラス フォーラム
- 1 LFS145 Class Forum
- 19 LFS200 Class Forum
- 736 LFS201 Class Forum
- 1 LFS201-JP クラス フォーラム
- LFS203 Class Forum
- 24 LFS207 Class Forum
- 292 LFS211 Class Forum
- 53 LFS216 Class Forum
- 41 LFS241 Class Forum
- 33 LFS242 Class Forum
- 31 LFS243 Class Forum
- 9 LFS244 Class Forum
- 27 LFS250 Class Forum
- 1 LFS250-JP クラス フォーラム
- 126 LFS253 Class Forum
- 924 LFS258 Class Forum
- 10 LFS258-JP クラス フォーラム
- 80 LFS260 Class Forum
- 122 LFS261 Class Forum
- 27 LFS262 Class Forum
- 77 LFS263 Class Forum
- 15 LFS264 Class Forum
- 10 LFS266 Class Forum
- 13 LFS267 Class Forum
- 16 LFS268 Class Forum
- 13 LFS269 Class Forum
- 191 LFS272 Class Forum
- 1 LFS272-JP クラス フォーラム
- 201 LFW211 Class Forum
- 147 LFW212 Class Forum
- 888 Hardware
- 211 Drivers
- 74 I/O Devices
- 44 Monitors
- 115 Multimedia
- 206 Networking
- 98 Printers & Scanners
- 85 Storage
- 744 Linux Distributions
- 88 Debian
- 64 Fedora
- 12 Linux Mint
- 13 Mageia
- 24 openSUSE
- 132 Red Hat Enterprise
- 33 Slackware
- 13 SUSE Enterprise
- 353 Ubuntu
- 466 Linux System Administration
- 37 Cloud Computing
- 66 Command Line/Scripting
- Github systems admin projects
- 94 Linux Security
- 77 Network Management
- 107 System Management
- 47 Web Management
- 59 Mobile Computing
- 21 Android
- 24 Development
- 1.2K New to Linux
- 1.1K Getting Started with Linux
- 523 Off Topic
- 126 Introductions
- 210 Small Talk
- 19 Study Material
- 781 Programming and Development
- 255 Kernel Development
- 492 Software Development
- 918 Software
- 255 Applications
- 181 Command Line
- 2 Compiling/Installing
- 75 Games
- 316 Installation
- 45 All In Program
- 45 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)